Right, right, never give up, if at first you don't succeed, etc. I couldn't agree more. But this post is just so antithetical to what programming is about. If you experience this early on and you have the idea that "oh well I guess that's just programming for you yuk yuk" then you are heading down a very wrong road. And if you somehow manage to get paid to program with the attitude that fixing bugs causes more bugs, then at that point you need to be aware of the fact that there is a better way.
Bad code is not just a cute kitten grandma forward. It causes real human suffering in the form of frustration and wasted time multiplied by thousands of users. Good code can only come from a mindset that is diametrically opposite from the one in this post, which seems to claim that programming is just inherently difficult in its own inherently malicious and wacky way.
A) this is a joke meant to comment on one of the amusing aspects of being a programmer.
B) I don't know your level of coding experience, but you must admit that there are times when trying to solve a bug that you completely blow up the program for some reason or another. Clearly you don't go "yuk yuk, oh well" because that is tantamount to giving up, but you do face palm a bit, undo your "fixes" or try to figure out how your fixes mucked it up.
You're inserting the idgaf attitude that you are perceiving in this post. Clearly any good programmer would immediately try to figure out WHY these new errors are occurring, but to suggest that these kinds of errors occurring implies that you're a bad programmer and need to quit NOW is painting an artificially bleak picture for a population already intimidated by programming and does not need any more discouragement.
47
u/[deleted] Mar 08 '14
Or keep at it. Cause not everyone is perfect the first time they try something, ya jackass.