Quote:Original post by Daaark
when you are working on GIMP
You mean the GNU Image Manipulation Program? How is that?
You know you're a crappy programmer when...
You mean the GNU Image Manipulation Program? How is that?
Quote:Original post by owlYes, I meant GIMP. That's what I wrote. Let's not derail the thread. It's just broken in every way, shape, and form. It's an epic fail from a programming/design standpoint. Everything in it is broken and gets subpar results. I use multiple paint programs and GIMP is outclassed by them all. I just keep it around to use a few random filters (and then promptly paste the result back into my better paint programs).Quote:Original post by Daaark
when you are working on GIMP
You mean the GNU Image Manipulation Program? How is that?
Quote:Original post by ToohrVyk
You're a bad programmer if you don't know how to make your program do what you want.
This doesn't mean that bad programmers never write programs that work—but when they do, they don't know why they work.
I'm not too sure about a crappy programmer but I'm thinking you might know you're a good programmer when a sense of humor must be suspended when a logic error is present.
I don't know how accurate it is but you might be a crappy programmer if you call your self Goober something. May just be true in my life, but it seems to be compiling. There are a couple of warnings...is that bad?
You are probably a crappy programmer if ... you are writing blogs about other programmers being crappy.
You're a bad programmer if you give up on an approach once you hit compile errors or bugs.
I know someone who does this, and instead of trying to figure out the cause of the problem he abandons the approach for something wildly different and invariably more complex. It's frustrating because the compile error or bug is usually really simple. It's just that he never bothers to spend a few minutes investigating it to unblock himself from the original, sensible solution.
Yes, there are cases where the problems aren't worth fixing, but please, at least investigate them. A smell that he hasn't investigated is when he says "it doesn't work" but is unable to elaborate.
I know someone who does this, and instead of trying to figure out the cause of the problem he abandons the approach for something wildly different and invariably more complex. It's frustrating because the compile error or bug is usually really simple. It's just that he never bothers to spend a few minutes investigating it to unblock himself from the original, sensible solution.
Yes, there are cases where the problems aren't worth fixing, but please, at least investigate them. A smell that he hasn't investigated is when he says "it doesn't work" but is unable to elaborate.
You're a bad programmer when you waste more time playing games than work on making them.
Guilty. =(
Guilty. =(
You're a crappy programmer when you say: "I can't solve this".
that'd actually make you a crappy anything.
that'd actually make you a crappy anything.
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement
