|
|
Silly you!
You forgot to add new tests to cover that code.
Try it now.
|
|
|
|
|
englebart wrote: You forgot to add new tests to cover that code.
Yes, yes, forgot. That's the ticket. Forgot the tests. 
Steve Martin: How many times do we let ourselves get into terrible situations because we don't say, "i forgot"?
You Can Be a Millionaire - YouTube[^]
|
|
|
|
|
"If you get a different error message, you're making progress."
modified 3-Nov-20 11:55am.
|
|
|
|
|
That quite possibly, is more help than we were given when first introduced to c++ templates at uni.
|
|
|
|
|
The old STL error messages were impressive! (and indecipherable)
|
|
|
|
|
I really really wish I didn't feel the full empathetic shock of identifying with your statement! Inside my bones, even!
|
|
|
|
|
I don't feel it in my bones until it happens after the second fix, when my mouse gets slammed violently. 
|
|
|
|
|
I've been finalizing a complete revamp of my Windows wrapper, which means four articles to make cohesive with each other, and several example programs which use the same code base. All of the programs are working correctly, and then I tried a feature that I know had worked in the past in one of the programs and I got an error message! Had to spend an hour to figure things out again! Uugh! Almost a mouse slam!
|
|
|
|
|
Be afraid! Be very afraid!
There must be a HUGE error lurking underneath. Remember the opening scene from Jaws 
Mircea
|
|
|
|
|
|
Time to go buy a lottery ticket! 
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
jeron1 wrote: Time to go buy a lottery ticket!
That's not a bad idea. But, I also will be careful of lightning strikes. 
|
|
|
|
|
but once I finally get it to work, I spend the next week second guessing myself if what I just did is a cob job, or a another example of very fine software engineering at its best.
|
|
|
|
|
|
You realize that if it ever needs an upgrade ... you'll be unable to touch it just in case ...
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
OriginalGriff wrote: You realize that if it ever needs an upgrade ...
Right. It's like the nuclear reactor I accidentally created. It's just sitting in the garage generating energy but I'm afraid to get too close to it to shut it down or use it.
|
|
|
|
|
I once wrote this expert system (in Fortran 77) for flight analysis. It was several thousand lines of code with a built in macro language to define state models and events to detect. It worked pretty much first time and I had 100 engineers using it for years without problems except for adding more features to make things easier to define, etc. I left the company a few years after implementing it but the system ran on and on. After I left they assigned a team of three programmers to update and or rewrite it but they apparently were too scared of breaking it to change anything. They attempted once to modify a small part of it and broke the whole thing - instant rollback time! They did managed to port it - with no code changes - to a newer mainframe but that was it for 20 years!
Next time I might do more documentation than auto-generated flowcharts! 
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
raddevus wrote: This is why I'll always enjoy software development. Because, every once in a while, I get something to work
 I'd say it comes with experience mostly. After 20+ years of doing this, I still occasionally throw a fist in the air when something complicated works the first time.
"Go forth into the source" - Neal Morse
"Hope is contagious"
|
|
|
|
|
|
This never happens to me. 90% of the time I write a method I forget to write the code that calls it. So I have at least one redo every time. ha.
|
|
|
|
|
Kschuler wrote: 90% of the time I write a method I forget to write the code that calls it. So I have at least one redo every time. ha.
Haha! I've done that quite a few times too. It's like, "Why isn't that stupid function working? It's not even doing anything". Then  "Need to add a call to it."
|
|
|
|
|
COBOL at least had a cross-reference listing.
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it.
― Confucian Analects: Rules of Confucius about his food
|
|
|
|
|
Gerry Schmitz wrote: COBOL at least
COBOL! COBOL! I'm triggered!
|
|
|
|
|
It was just your imagination running away with you.
#SupportHeForShe
Government can give you nothing but what it takes from somebody else. A government big enough to give you everything you want is big enough to take everything you've got, including your freedom.-Ezra Taft Benson
You must accept 1 of 2 basic premises: Either we are alone in the universe or we are not alone. Either way, the implications are staggering!-Wernher von Braun
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
