Main Area and Open Discussion > Living Room
Signs You're a Crappy Programmer (and don't know it)
app103:
You know those crappy programmers who don’t know they are crappy? You know, they think they're pretty good, they spout off the same catch phrase rhetoric they've heard some guru say and they know lots of rules about the "correct" way to do things? Yet their own work seems seriously lacking given all the expertise they supposedly have? You don’t know any programmers like that? Come one, you know, the guys who are big on dogma but short on understanding. No, doesn’t sound familiar?
--- End quote ---
http://damienkatz.net/2006/05/signs_youre_a_c.html
Renegade:
That was a good list.
I know that sometimes I write just total crap. That's usually because I'm trying to get something done quickly and ignore the best way to do things. Most often those aren't for release though. I take more time when working towards a release, but I still do take shortcuts from time to time.
The way the images are done in the Anti-Christ Hunter isn't the best way at all. I've statically added all the images instead of having a dynamic method to do it. Not the best way, but a quick and easy way. It would have been better to do it dynamically so that images can be easily added.
Often there's no "right" way to do things, just different ways. It all depends on what you need to do.
I recently corrected someone on a programming issue where they were dealing with a URL, but treated it as a string. The logic behind that is IMMENSE and very difficult. The best way to do it is to cast the URL as a URI type and then deal with it. You have MUCH LESS code then, less prone to bugs, it's more reliable, and a LOT less work. Treating it as a string is in every way inferior. So sometimes there are situations where there is a clearly superior way to do things.
Ralf Maximus:
TOP TEN SIGNS YOU'RE A CRAPPY PROGRAMMER
10. You remove all the comments you find because they take up valuable RAM.
9. You've locked yourself out of your own garage because you've misprogrammed the remote.
8. You discover all the error handlers in the project are named after you.
7. Instead of errors, your compiler generates terrorist alerts.
6. Your proudest achievement: Lead Developer for Windows ME Microsoft Bob.
5. The title on your business cards: "Shit For Brains".
4. You have your own security detail -- as protection from the QA team.
3. Your idea of "optimization" is to delete the stuff you don't understand.
2. You get flowers and expensive gifts after each software release. From the competition.
1. Your version of "Hello World" crashes.
app103:
6. Your proudest achievement: Lead Developer for Windows ME.
-Ralf Maximus (December 01, 2007, 09:04 PM)
--- End quote ---
>:(
Ralf...Stop making me defend WinME. Go pick on MS Bob, or Vista, or WinCE 3.0/PocketPC 2000. Leave my faithful, hard working ME alone or I'll send an army of ME-tans to your house to beat you with scallions. :-*
Ralf Maximus:
You know, you're right.
Microsoft Bob sucked harder than anything else I've ever seen. Bad idea, poorly executed, for a market that didn't exist.
Besides, "Microsoft Bob" is funnier. Thanks; I changed it.
Navigation
[0] Message Index
[#] Next page
Go to full version