Signs You’re a Crappy Programmer

Thursday, August 30th, 2007

Really old blog entry: Signs You’re a Crappy Programmer (and don’t know it).

Check out the comments. They’re pretty funny. Especially this one:

Alright, so I’m a student at the Milwaukee School of Engineering and currently studying Software Engineering. This is a very prestigious school (4th in the nation), and they courses dedicated to Design Patterns. Can they be all that bad? From what we’ve had drilled into our heads, design patterns should be used whenever possible. Remember the whole “low coupling, high cohesion” design tip? Using patterns allows for just that. We recently completed a lab that combines multiple, eight to be exact, design patterns.

Another thing I’d like to mention is that most earlier generation programmers have learned to code a certain way and refuse to change it. More companies are adopting the Personal and Team software processes (PSP and TSP) that are saving them millions of dollars a year on development. Part of those processes are doing preliminary and detailed design of your program, which includes making detailed UML diagrams.

Well, whatever…us n00bs are going to take over your jobs someday, or at least we’ll end up teaching all your old folks the right way to program. IMO, your list sucks. Oh, and Java is going to take over — slowly but surely. Peace.

It’s either sarcasm, or this guy’s gonna have a hard time in the Real World. ;-)

Anyway, there’s only one sign I’d like to add to his list: You’re a crappy coder if you’ve ever said “Never do Foo.“.