Signs You're a Crappy Programmer (and don't know it)
damienkatz.net
Signs You're a Crappy Programmer (and don't know it)
1–10 of 66 posts
Re: Signs You're a Crappy Programmer (and don't know it)
#2Oh, well I'm not crappy then. Neither I'm a good one though...
Re: Signs You're a Crappy Programmer (and don't know it)
#3I think it should have been "Signs you are a day coder (and don't know it)"
I am amazed how many programmers I have worked with who are not up to date and just do their job and are not interested in it.
Re: Signs You're a Crappy Programmer (and don't know it)
#4"...and it often simplifies the code to have multiple returns."
Today. And what happens after 10 other programmers modify your slick little multi-return function? Nobody will ever be able to modify it again because the entries and exits are lost among the garbage. This is the ongoing debate I've had for years with "clever programmers". They're missing one critical point: the guidelines of structured programming are not meant to make your life easier; they're meant to keep the code alive longer by making life easier for the poor schmuck who has maintain it (usually me).
Another Sign You're a Crappy Programmer:
You make your own rules in direct violation of effective established principles because you think you know better.
Re: Signs You're a Crappy Programmer (and don't know it)
#510 Real Signs You're a Crappy Programmer:
10. The exact same code is in multiple places because you didn't bother to put in into a common function.
9. You have error codes in functions, but never bother to look at them (a sure sign that testing was never finished).
8. You have early exits from loops because you don't know how to properly code a recursion.
7. You execute too much code because you don't know the difference between "if" and "case".
6. You use 10 lines of code when 1 line would do because you don't know any better.
5. You need to run batch jobs from time to time to clean up your data base because you don't know how to debug well enough to find what's messing it up.
4. A third grader doesn't know what your variable names mean.
3. You think "Third Normal Form" is paperwork you need to fill out for one of your 8 bosses.
2. No programmer who has to maintain your code would ever want to work with you.
1. Any programmer that has to maintain your code would be more than happy to accept the consequences of first degree murder.
Re: Signs You're a Crappy Programmer (and don't know it)
#610 Real Signs You're a Crappy Programmer: 10. The exact same code is in multiple places because you didn't bother to put in into a common function. 9. You have error codes in functions, but never bother to look at them (a sure sign that testing was never finished). 8. You have early exits from loops because you don't know how to properly code a recursion. 7. You execute too much code because you don't know the differ…
0. You refuse to use recursion even when working with a language that supports it properly because you think it's horribly slow.
Re: Signs You're a Crappy Programmer (and don't know it)
#710 Real Signs You're a Crappy Programmer: 10. The exact same code is in multiple places because you didn't bother to put in into a common function. 9. You have error codes in functions, but never bother to look at them (a sure sign that testing was never finished). 8. You have early exits from loops because you don't know how to properly code a recursion. 7. You execute too much code because you don't know the differ…
"8. You have early exits from loops because you don't know how to properly code a recursion."
Wow. Not every problem calls for recursion. If you really hate early exits from loops, maybe you should just code the loop's condition differently.
Re: Signs You're a Crappy Programmer (and don't know it)
#810 Real Signs You're a Crappy Programmer: 10. The exact same code is in multiple places because you didn't bother to put in into a common function. 9. You have error codes in functions, but never bother to look at them (a sure sign that testing was never finished). 8. You have early exits from loops because you don't know how to properly code a recursion. 7. You execute too much code because you don't know the differ…
(6) Happens even when you know better.
(10) Good programmers don't repeat themselves, true, and to continually improve as a programmer it is important to patiently do everything correctly the first time. However, obsessing over a few bits of code duplication is often a complete waste of time.
Re: Signs You're a Crappy Programmer (and don't know it)
#9"...and it often simplifies the code to have multiple returns." Today. And what happens after 10 other programmers modify your slick little multi-return function? Nobody will ever be able to modify it again because the entries and exits are lost among the garbage. This is the ongoing debate I've had for years with "clever programmers". They're missing one critical point: the guidelines of structured programming are n…
Early returns make code more readable. I'd rather detect an error and bail then have a slew of nested ifs.
It isn't always about being clever.
Re: Signs You're a Crappy Programmer (and don't know it)
#1010 Real Signs You're a Crappy Programmer: 10. The exact same code is in multiple places because you didn't bother to put in into a common function. 9. You have error codes in functions, but never bother to look at them (a sure sign that testing was never finished). 8. You have early exits from loops because you don't know how to properly code a recursion. 7. You execute too much code because you don't know the differ…
(6) Happens even when you know better. (10) Good programmers don't repeat themselves, true, and to continually improve as a programmer it is important to patiently do everything correctly the first time. However, obsessing over a few bits of code duplication is often a complete waste of time.
"...obsessing over a few bits of code duplication is often a complete waste of time."
For you, maybe. But what about the guy who applies enhancements 3 years later and has trouble getting through testing because the exact same code was somewhere else and difficult to find because of the 67 mods since then.
Minutes "obsessing" today usually saves hours testing tomorrow.