|
This paper is not meant for grading programmers, it was intended to be read by programmers who trust their ability to judge when something is a sign of bad practice, and when it's a consequence of special circumstances.
Signs that you're a bad programmer[^]
Twenty years from now you will be more disappointed by the things that you didn't do than by the ones you did do. So throw off the bowlines. Sail away from the safe harbor. Catch the trade winds in your sails. Explore, Dream. Discover.
|
|
|
|
|
Oooooh. Not understanding pointers makes you a poor programmer. Complete and utter rubbish - and I speak as someone who cut my teeth on pointers. JavaScript - no pointers. .NET - pointers abstracted away from you. Java - the same.
I've seen some amazing code produced by brilliant developers who wouldn't know what a pointer was if it bit them.
|
|
|
|
|
The page also lumps references in with pointers, and "not understanding references" is kind of a bad thing..
|
|
|
|
|
Unbeatable. Easily the best xkcd I'm yet to view. Thanks.
Make it work. Then do it better - Andrei Straut
|
|
|
|
|
He goes on to say that many languages use references in place of pointers, but these only protect against certain kinds of pointer errors. I guess you didn't read the next paragraph having given up in disgust.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
