Two lines of code I wrote today with a straight face (at least for a while)
-
A long time ago I took a programming class from Dan Saks, one-time secretary of the ISO C++ standardization committee. He said something to us which has stuck with me ever since, and has led to a profound reduction in the number of comments I write: "If you can, say it in code. If you can't, only then say it in a comment." While we do maintain change history in our source, my comments now tend to serve other purposes than simple documentation. For example, our code base is in the neighborhood of 3 million lines so navigation can be a problem. Comments can serve as markers for 'find in files' destinations when Intellisense doesn't work.
Software Zen:
delete this;
One of my mentors once stated "The comments are the part of the code that even the compiler cannot understand"
-
An old C system I once worked on had a routine `abortOrphans()`. :laugh:
veni bibi saltavi
-
// terminate users \_Users\_Terminate();
:-D
Software Zen:
delete this;
And I thought the problem was: _Users_Terminate( IgnoreUser=Me ); // Bug found that after terminating my user, program stopped...
-
There's no such thing as a "line of code" in C-style languages.
You mean I've spent all these years doing... nothing? :wtf:
Software Zen:
delete this;
-
An old C system I once worked on had a routine `abortOrphans()`. :laugh:
veni bibi saltavi
Many years ago my team was working with an inherited system based on FoxPro. The original designer had used abbreviated table names like ASS instead of Assignment. A normally straight laced co-worker bust out laughing one day when he had to write a SQL statement "INSERT INTO ASS ..." :laugh:
Outside of a dog, a book is a man's best friend; inside of a dog, it's too dark to read. -- Groucho Marx
-
my hubby used to work helldesk in college and he said he kept a paperclip around for rebooting the imacs and an icepick around for rebooting their users.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
-
An old C system I once worked on had a routine `abortOrphans()`. :laugh:
veni bibi saltavi
-
// terminate users \_Users\_Terminate();
:-D
Software Zen:
delete this;
-
A tad BASIC, but sounds like fun.
Software Zen:
delete this;
-
Many years ago my team was working with an inherited system based on FoxPro. The original designer had used abbreviated table names like ASS instead of Assignment. A normally straight laced co-worker bust out laughing one day when he had to write a SQL statement "INSERT INTO ASS ..." :laugh:
Outside of a dog, a book is a man's best friend; inside of a dog, it's too dark to read. -- Groucho Marx
In a similar tone... Many years ago, we had a small network of Sun machines. The machine names followed the names of the planets in our solar system. The QA guy (who was a 1st-order asshat) was incensed when he was given the machine named... wait for it... you know it's coming... Uranus.
Software Zen:
delete this;
-
An old C system I once worked on had a routine `abortOrphans()`. :laugh:
veni bibi saltavi
Years ago I implemented a message dispatch function name WhoCares(). It stuck around that way until a coworker added a popup dialog box to it that displayed a tracing message usually written to a log file. At some point that popup appeared and the customer service folks had kittens over it. Apparently they read it as "we don't care about this", when in reality the WhoCares() function was deciding which routine to pass the message on to, you know "who cares about processing this, I'll pass it on to them". Anyway, the customer service folks didn't have a sense of humor about it and I was forced to change it's name to the innocuous "EventProcessor". To this day I still refer to it as "WhoCares". :)
-
An old C system I once worked on had a routine `abortOrphans()`. :laugh:
veni bibi saltavi
In a CRM I worked on, had a method that cleaned up sales records,securities and associations for reps, I look at it quite fondly on a regular basis. KillRep(x)