The worst program I ever worked on
jacquesmattheij.com
The worst program I ever worked on
1–10 of 136 posts
Re: The worst program I ever worked on
#2Needless to say, maintaining his code took some getting used to.
Re: The worst program I ever worked on
#3By the way, if you're naming a company, life will be easiest with a made-up word, but maybe you got bucks.
Re: The worst program I ever worked on
#4What goes on in someone's mind that says: "Maybe if I spend some time making my source code hard to understand I can better preserve my job." ?
In reality all it does is slow them down, waste their time and lead to the firing of the developer. (At which point we get to hear funny stories from people like jacquesmatteij)
If that time was spent improving/refactoring their code and working on new things, they'd actually have the job security they were so desperately seeking.
Re: The worst program I ever worked on
#5When a company I worked for was bought the new companies tried to lay of some (most) of the employees. At this time our team was working on a product that was to a large degree implemented in Scheme (because management didn't really care about the programming language). I quit at the company (for unrelated reasons) soon thereafter, but it seems that my colleague (with whom I've implemented the system) had quite a good job security at this time.
Re: The worst program I ever worked on
#6We've all read bad code with bad names that nonetheless "works" (except perhaps for the occasional minor glitch). This is perhaps just one that combines poor programming style with a mis-placed sense of humor.
Re: The worst program I ever worked on
#7Call me Captain Obvious, but I feel like quite often the time spent in obfuscating code in many cases might be a major component of why programmers that do this sort of thing get fired in the first place. What goes on in someone's mind that says: "Maybe if I spend some time making my source code hard to understand I can better preserve my job." ? In reality all it does is slow them down, waste their time and lead to…
Re: The worst program I ever worked on
#8Call me Captain Obvious, but I feel like quite often the time spent in obfuscating code in many cases might be a major component of why programmers that do this sort of thing get fired in the first place. What goes on in someone's mind that says: "Maybe if I spend some time making my source code hard to understand I can better preserve my job." ? In reality all it does is slow them down, waste their time and lead to…
[deleted]
Re: The worst program I ever worked on
#9Re: The worst program I ever worked on
#10One student named all his variables in phonetic chinese (using the utf8 character set of course).
Another student named all his variables after superheros.