Client asks for X Implement what client actually needs which is Y Client makes dozens of changes and insane demands now asking for Z which has nothing to do with X or Y Collect paycheck GOTO line 1
Programming is the kind of job where you'll have an eight hour whiteboard interview on the topic of B-trees vs red-black trees and compiler lexical analysis theory to get a job, where your coworkers don't understand the difference between a word document and a database.
Starting Score:
1
point
Moderation
+4
Insightful=2,
Informative=2,
Total=4
Extra 'Insightful' Modifier
0
Karma-Bonus Modifier
+1
Total Score:
5
(Score: 2) by DannyB on Thursday May 24 2018, @02:59PM
(6 children)
Do what I do to fix bugs - wrap everything in a giant try block followed by an empty catch block. Your program will continue working like a charm, if your customer doesn't care which places the decimal points go in his payroll system.
(Score: 0) by Anonymous Coward on Wednesday May 30 2018, @10:05PM
by Anonymous Coward
on Wednesday May 30 2018, @10:05PM (#686511)
I don't know if you are serious, and I hope you aren't.
But, I am sad to say I have seen this behavior in legacy code my team has had to maintain. When I asked devs who had been here a long time why there were so many empty catch blocks in the code, they said former management wanted to reduce the amount of errors the service produced, and gave a ridiculous timeframe to get the work done. The only solution was to remove the logging statements in the catch blocks. This is a true story. :(
how many unknown bugs are there, and how long will they take to fix
A wise man once said:
Reports that say that something hasn't happened are always interesting to me, because as we know, there are known knowns; there are things we know we know. We also know there are known unknowns; that is to say we know there are some things we do not know. But there are also unknown unknowns – the ones we don't know we don't know. And if one looks throughout the history of our country and other free countries, it is the latter category that tend to be the difficult ones.
There are also the swept-under-rug knowns. Eventually that tiny bump in the carpet becomes big enough to trip over making it a don't-trip-over-the-imaginary-unknown.
-- People today are educated enough to repeat what they are taught but not to question what they are taught.
(Score: 5, Insightful) by VLM on Wednesday May 23 2018, @03:27PM (8 children)
For a couple decades the methodology I used was
Client asks for X
Implement what client actually needs which is Y
Client makes dozens of changes and insane demands now asking for Z which has nothing to do with X or Y
Collect paycheck
GOTO line 1
Programming is the kind of job where you'll have an eight hour whiteboard interview on the topic of B-trees vs red-black trees and compiler lexical analysis theory to get a job, where your coworkers don't understand the difference between a word document and a database.
(Score: 2) by DannyB on Thursday May 24 2018, @02:59PM (6 children)
I wish I could mod you up further.
Manager: how many unknown bugs are there, and how long will they take to fix. I need to know by tomorrow morning.
People today are educated enough to repeat what they are taught but not to question what they are taught.
(Score: 2, Insightful) by Ethanol-fueled on Saturday May 26 2018, @12:16AM (3 children)
Do what I do to fix bugs - wrap everything in a giant try block followed by an empty catch block. Your program will continue working like a charm, if your customer doesn't care which places the decimal points go in his payroll system.
(Score: 0) by Anonymous Coward on Sunday May 27 2018, @01:17AM
I have no words.
Yes. I do. Don't do this in powershell. Try doesn't always catch clean which can result in broken program.
(Score: 0) by Anonymous Coward on Wednesday May 30 2018, @10:05PM
I don't know if you are serious, and I hope you aren't.
But, I am sad to say I have seen this behavior in legacy code my team has had to maintain. When I asked devs who had been here a long time why there were so many empty catch blocks in the code, they said former management wanted to reduce the amount of errors the service produced, and gave a ridiculous timeframe to get the work done. The only solution was to remove the logging statements in the catch blocks. This is a true story. :(
(Score: 0) by Anonymous Coward on Sunday June 10 2018, @01:44AM
Please don't work on anything important in the real world.
(Score: 2) by isostatic on Saturday June 02 2018, @08:49PM (1 child)
how many unknown bugs are there, and how long will they take to fix
A wise man once said:
(Score: 2) by DannyB on Monday June 04 2018, @01:32PM
There are also the swept-under-rug knowns. Eventually that tiny bump in the carpet becomes big enough to trip over making it a don't-trip-over-the-imaginary-unknown.
People today are educated enough to repeat what they are taught but not to question what they are taught.
(Score: 0) by Anonymous Coward on Wednesday June 06 2018, @12:43AM
Ugh, what a complete lack of proper flow control.
while PayCheck.clears():
X = Client.last_request()
Y = Client.actual_needs()
Developer.program(Y)
Z = Client.last_request()
assert X != Y != Z