5 ms·
Advice to a young programmer
- morisy 18y agoI think a lot of that is great advice for a thirteen-year-old just getting feet wet, particularly the suggestion about diving in and hacking around. I self-learned a whole lot about programming (and game design) with http://www.alice.org/ http://www.alice.org/ around the same age. It gives you a built-in 3D engine but learning more and more about Python lets you do cooler simulations. Maybe he should check it out?
- pavelludiq 18y agoWow, i started learning seriously 6-7 months ago and i basically did all that. I even have most of the recommended books.
- emmett 18y agoGenerally good advice, but I disagree with #9 (avoid debuggers, learn to unit test). Unit testing is important perhaps if you have a large project with many contributors, but no good hackers I know learned to program with testing and "Best Practices".
- jgrahamc 18y agoI disagree (but that I did write TFA). I have a piece of commercial software I sell, it has an extensive set of unit tests. I'm the only developer and I wrote them because I need to know that if I ship a new version to my customers that I haven't broken anything. Unit tests give me the flexibility to refactor, improve, bug fix, etc. with the assurance that I'm not messing things up. It would be very costly for me to ship broken code to my customers.
- emmett 18y agoFor sure, but did you start learning to program by using unit tests? "Use unit tests" is great advice for a developer shipping commercial software, and bad advice for a 13 year old who wants to learn to code.
- Tamerlin 18y agoThat sounds contradictory to me. If you learned to program without testing and best practices, then you're not a good programmer, you're just a hack. I don't agree about the debugger though... it's a tool, when used properly a helpful tool, so learn to use it.
- emmett 18y agoThe article is about advice you'd give to a 13 year old who wanted to learn to program, not about how to become a professional software developer. Unit tests are not necessary to learn to program, and thus should be left for later.
- gojomo 18y agoavoid debuggers I'm of the opposite school of thought: stepping through code with a nice debugger -- even non-buggy code -- helps build the internal mental model of how code works, so you can more easily 'run code in your head'.
- parenthesis 18y agoI would add: find like-minded people (among your peers, and older 'mentors').
- j2d2 18y agoPerhaps even recommend IRC. IRC has developed the brass balls on many of my programming friends. Though it hurts at first, I'd recommend it to anyone seriously considering programming professionally as a psychological benchmark for having ones logic and presentation brutally criticized.
- cliff 18y agoI don't know about you guys but I've never done this whole 'practice coding with simple applications' thing. When I started writing software I did it with specific goals in mind, things that would either help me or others, and then found out everything I needed to to accomplish that task. Everyone has their own learning style, but this one seems to be rarely presented.
- hugh 18y agoDidn't everybody want to be a games programmer when they were thirteen?
- warwick 18y agoWhy would debuggers or unit testing be an exclusive choice? I see unit tests as a way to work in the existing code without breaking it, and a debugger as a way to figure out what's happening when you've broken something.