GL (not her real name) was tasked by her boss to find out why that stupid program had so many bugs reported during the recent live test. Having patched it more times than most, she asked me to give an analysis.
Jo: I don't know what to tell you. So just listen can already, no need write.
[Mentally prepare points]
Jo: Well firstly, the program is huge. So people are afraid to change anything beyond what they know... Hey, stop writing! Just out of Uni, got student sickness, is it?
[She sat on her hands and looked mildly sheepish]
GL: I'm like this in Uni...
Jo: They go for the safe path. For example, the tabs "Basic data 1" and "Basic data 2" can be called 3 times in the background, each updating a different thing. People use the method which they know is safe. Which is to open the program and dump their information in, not caring if there's another portion that has a similar function.
Jo: Second is the size of the program.
GL: How huge?
Jo: Well, there's 50 odd notifications types, from Y0 to ZZ. I estimate about 60 files.
GL: Files?
Jo: Ya, programs, source-codes. Stop writing!
GL: Don't worry, I won't quote you.
Jo: ...
Jo: Thirdly, the documentation is in a poor state. They promised but did not deliver. They delivered these features but did not document it. They implemented these features but they don't work... Stop writing...
For the rest of the "session", I showed her the size of the program. I related to her the use of includes by comparing it to C. I gave her examples of common errors reported. Finally, armed with her notes, she was contented. Wonder what good it'll do.
[The above post contains some inaccuracies due to the process of condensation and a need for drama.]
No comments:
Post a Comment