|
Well, that sounds like Nagy ! 
presumably you are referring to Gordon's cases !!
Thanks,
Milind
|
|
|
|
|
Spam removed.
modified 22-May-15 15:35pm.
|
|
|
|
|
Not surprising. When I'm in the integration testing or maintenance phase of an application, each bug is usually a significant context switch -- what steps create the bug, what data interacts with creating the bug, what's the code path, verifying that the test is doing the right thing or that the user reported the correct steps, etc. It can take a while just getting all the info in place to understand the issue, then there's the "do I write a test specifically for this bug?" path, fixing the bug, retesting, running all the integration tests again to make sure something else didn't break.
But the context switch itself can be almost painful and it takes a certain discipline not to wonder off to Code Project and procrastinate for a good amount of time.
Hmmm...speaking of which.... 
Marc
|
|
|
|
|
I found the UI of this web page quite poor...
Had to scroll down to see the ad popup which blacken the page...
Whenever I mouse over a section it greenify it making it hard to read...
|
|
|
|
|
Quote: The Insider Five minutes to fix, 10 minutes to compile and text, three hours to get rebased on the main branch
1 day to QA, 2 weeks to get deployed.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
the problem I usually find is that so called IT departments or contractors just don't listen when you explain what they need to do, think they know it all or plain just don't it. this then requires more too-ing and fro-ing getting them back on the phone to set the permission to that folder, sql database or login that you specifically told them they must do when installing, so the first you know it is that an irate customer cant do something so calls you first as its your product and you have to go through the whole process again - grrrrrr
|
|
|
|
|
The way it usually goes is you get a call that something isn't working, so you email them the installation docs, instructions or prerequisites (again!) and get them to check they have followed every step exactly. The reply comes back five minutes later "It's working now".
|
|
|
|
|
I had a good one today when a local IP address to a device 'disappeared' after the new IT contractors had been messing with the router - after mucho discussion we had to get the original guy back in sort it, which he did, and the new guy rang me later to tell me 'Ive sorted it now' - I couldn't let that one go so let him know in no uncertain terms that HE hadn't sorted it at all, it was him that caused the problem, wasted all our time & cost the customer money, and yet expected us to somehow be thankful HE'D solved the problem - my contact told me the new guy looked about 5 years old and seemed a tad upset, but my empathy with 'experts' vanished many years ago so I didn't feel in the least bit bad about it lol. GL
|
|
|
|
|
I was walking around campus today wondering where all the high end German made cars were hiding and then I remembered that the students are away on break.
|
|
|
|
|
Why is it that we as programmers hate to document?
I document code as I go but I write articles for my site on projects and libraries I create and I suck at it, put off doing it and when I do get down to writing it's a slow tedious process.
New version: WinHeist Version 2.1.0
There's a fine line between crazy and free spirited and it's usually a prescription.
I'm currently unsupervised, I know it freaks me out too but the possibilities are endless.
|
|
|
|
|
We are used to writing for a smarter user-base than the documentation's target audience.
|
|
|
|
|
The problem is I understand what I write but few others do. 
New version: WinHeist Version 2.1.0
There's a fine line between crazy and free spirited and it's usually a prescription.
I'm currently unsupervised, I know it freaks me out too but the possibilities are endless.
|
|
|
|
|
Use examples.
Everyone understands and example
PooperPig - Coming Soon
|
|
|
|
|
I've noticed that Mike. 
Life is like a s**t sandwich; the more bread you have, the less s**t you eat.
|
|
|
|
|
Tragic and true.
Mislim, dakle jeo sam.
|
|
|
|
|
I usually try to enforce a code freeze a few weeks before release. (depending on the size and complexity of the package). In that time I make sure to write the documentation and create install procedures and the like. 
|
|
|
|
|
My code is self-documenting
I hate documenting my code (i.e. writing manuals), unless it is to teach others how to use a certain technology (like in my blog or articles).
And I'm not particulary bad at it.
But I do have a degree in Media and Journalism, so I may not be your average documentor
My blog[ ^]
public class SanderRossel : Lazy<Person>
{
public void DoWork()
{
throw new NotSupportedException();
}
}
|
|
|
|
|
Sander Rossel wrote: My code is self-documenting
As it should be.
New version: WinHeist Version 2.1.0
There's a fine line between crazy and free spirited and it's usually a prescription.
I'm currently unsupervised, I know it freaks me out too but the possibilities are endless.
|
|
|
|
|
The Documentors - weren't that nasties in Harry Potter?
Life is like a s**t sandwich; the more bread you have, the less s**t you eat.
|
|
|
|
|
Almost 
My blog[ ^]
public class SanderRossel : Lazy<Person>
{
public void DoWork()
{
throw new NotSupportedException();
}
}
|
|
|
|
|
PhilLenoir wrote: The Documentors - weren't that nasties in Harry Potter?
No, they had a different name and were just the end result of trying to document something.
|
|
|
|
|
Sander Rossel wrote: I hate documenting my code
One company I worked for, we had documentors that created the documentation in parallel with us.
We'd occasionally upset the documentors when we found we had to change something, but we tried to keep it to a minimum.
That worked fairly well. Particularly since English was no longer the primary language for the programmers.
Psychosis at 10
Film at 11
Those who do not remember the past, are doomed to repeat it.
Those who do not remember the past, cannot build upon it.
|
|
|
|
|
Sounds a bit like pair programming, but with one doing documentation.
That might actually work...
My blog[ ^]
public class SanderRossel : Lazy<Person>
{
public void DoWork()
{
throw new NotSupportedException();
}
}
|
|
|
|
|
I really enjoyed it.
One case in particular, I had written what I called the "Custom Output Processor" for our database product. I had implemented an RPN style calculator so you could do math before displaying the results on the report. It also had commands for copying fields to the report. It was driven by a table of opcodes and arguments that were interpreted by the code. I had user opcodes like RCL, STO, PRT.
I was writing the next generation and wanted to make the processing orthogonal and was merrily adding new opcodes like INP, WRT, etc., and the documentor threw up her hands and declared it unteachable.
That caused me to pause and recognize she was correct. I redesigned it replacing all the different user opcodes with MOV and the arguments determined the internal opcode for processing.
I was particularly pleased because I made it code compatible with the earlier version. You may have written your processing in the earlier version with RCL and STO, but when you opened them in the newer version, you'd see them converted to MOV with the arguments indicating if you were reading a field, register, or an output field.
It really helped having a "non-technical" person commenting on what you were creating.
(BTW the database was The Data Factory published by Micro Lab, Inc for the Apple II)
Psychosis at 10
Film at 11
Those who do not remember the past, are doomed to repeat it.
Those who do not remember the past, cannot build upon it.
|
|
|
|
|
BrainiacV wrote: It really helped having a "non-technical" person commenting on what you were creating.
Sounds useful.
BrainiacV wrote: The Data Factory
Haven't heard of it.
BrainiacV wrote: Micro Lab, Inc
Haven't heard of it...
BrainiacV wrote: Apple II
Haven... Oh wait, I know Apple! The Apple II was released about ten years before I was even born (not to make you feel old or anything, I guess I'm just young)
My blog[ ^]
public class SanderRossel : Lazy<Person>
{
public void DoWork()
{
throw new NotSupportedException();
}
}
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
