|
You realize there is a bug on line 768,321? 
The only instant messaging I do involves my middle finger.
English doesn't borrow from other languages.
English follows other languages down dark alleys, knocks them over and goes through their pockets for loose grammar.
|
|
|
|
|
What concerns me is the number of exceptions that are thrown (silently) as the program runs.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Hopefully they are logged, rather than swallowed?
He asked, fully assuming the complete opposite... 
The only instant messaging I do involves my middle finger.
English doesn't borrow from other languages.
English follows other languages down dark alleys, knocks them over and goes through their pockets for loose grammar.
|
|
|
|
|
I'd argue that thousands of exceptions in a log file isn't much better then silently swallowing them.
It's interesting that interview questions often revolve around try/catch/finally. This bit is easy, its determining the flow of execution under errored conditions that is the tricky bit.
Regards,
Rob Philpott.
|
|
|
|
|
Logged? Why? Isn't empty catch blocks a good practice any more?
"Bastards encourage idiots to use Oracle Forms, Web Forms, Access and a number of other dinky web publishing tolls.", Mycroft Holmes[ ^]
|
|
|
|
|
Good practice is a messagebox that says, "The program was going to crash, but the programmer [insert name here] was too awesome to let that happen."
Not to mention lots of smiley faces to show how much of a good thing it is.
|
|
|
|
|
Don't forget the cat picture. It always works. Or may be a link to pr0n website. Users tend forget all issues if we do that.
"Bastards encourage idiots to use Oracle Forms, Web Forms, Access and a number of other dinky web publishing tolls.", Mycroft Holmes[ ^]
|
|
|
|
|
An animated cat gif, too. Don't forget to make the messageboxes recursive, in case the animation has an error. Moar Kittiezz!!!1!
d@nish wrote: Or may be a link to pr0n website. Users tend forget all issues if we do that.
Obligatory Dilbert comic[^]
|
|
|
|
|
In my current development I have a msg box that pops up and says "This is gonna be so sweet when we get this implemented!".
|
|
|
|
|
Imagine a brace mismatch at line 249403.  
|
|
|
|
|
That's why God made compilers.
Software Zen: delete this;
|
|
|
|
|
God made compilers to imagine brace mismatches?
I think we're really screwed...
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
I'm saying if your compiler doesn't catch brace mismatches, you've got bigger problems.
Software Zen: delete this;
|
|
|
|
|
It is not the problem in compiler. You still need to fix it, but if you go after auto-indent 
It is good that "God" (if that is the developer nickname) made better IDEs catching the matching opening brace.
|
|
|
|
|
John Simmons / outlaw programmer wrote: After recovering from the mental whammy imposed by a 5-million line error,
is this an ACA reference ?
|
|
|
|
|
On a good day I used to be able to type 100WPM. Not to say my day is all typing but if I wanted to churn out mounds of Government approved code that would be about a months to do a million lines. Really easy if you include comments generated by a tool and auto generated CRUD code. Add another developer and a million lines isn't so difficult to achieve. The true genius is doing the same thing in 80,000 readable lines : )
(Not implying anything just a related statement)
|
|
|
|
|
Well, write in Java, document getter and setters, done - application do nothing with more than 200,000 lines of code.
|
|
|
|
|
write in C#, even shorter! 
|
|
|
|
|
John Simmons / outlaw programmer wrote: The final count is 1,061,156
After clicking the 'show disassembly' button? 
"Real men drive manual transmission" - Rajesh.
|
|
|
|
|
We did a line count 3-4 years ago. We had 800K to 1.7M lines per product across five products, with some of the code shared between products, managed by a team of six. We've never placed much stock in lines of code, but it was a metric we needed for an IRS evaluation of our R&D program. They originally wanted a paper listing of everything we'd written over the preceding five year period.
Snicker.
We computed that printing the listing for all of the code would require a fairly standard roll of paper, 40 inches in diameter. It would have taken a little over an hour to print on one of our machines (we make commercial ink-jet printing systems). We were sorely tempted to do it, just so we could deliver this monstrosity to the IRS office. As it was, we delivered a spindle of ~100 DVD's plus a directory listing on paper of each disc which took up an entire case of letter paper. Bastards.
Software Zen: delete this;
|
|
|
|
|
I wouldn't like to be the guy that has to review it, either way.
|
|
|
|
|
SortaCore wrote: I wouldn't like to be the guy that has to review it, either way.
Are you kidding?
We're talking about tax inspectors!
They live for this stuff -- I'd bet the guy assigned to it cancelled his holidays, he was having so much fun.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
He's probably still going through it, patiently correcting bugs and standardising it. He just needs a second project like that and he's set for life.
|
|
|
|
|
I heard third-hand that they delivered the DVD's and the directory listing to the IRS, the IRS guy essentially checked a box on a form, and they dumped the whole mess in the secure shredder while our lawyer watched.
We could have delivered a spindle of blank DVD's and a box of blank paper, and saved me a couple hours and our technician a couple weeks work (he did the DVD duplication and the directory listings).
Software Zen: delete this;
|
|
|
|
|
Your tax dollars at work for you.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
