Things I Wish Someone Had Told Me When I Was Learning How to Code

The article says learning to code is less about proving intelligence and more about building something concrete. It emphasizes having a clear goal, using tools that help you make the thing you want, and keeping at it when tutorials stop being enough.

It also argues that coding is a skill, not a secret club. The author notes that failure is normal, disagreements over style are common, and worries about being a “real” coder or having enough geek cred should not get in the way of making progress.

Reading notes

#

• Start with a specific thing you want to build, because “learn to code” is too vague to guide study.
• Coding is presented as a learned skill, with grammar, vocabulary, tools, and techniques that can be used or changed.
• Pointers and recursion are described as useful concepts, but not the main measure of whether someone can build things.
• Beginners and experienced programmers both run into code that does not work, and the response matters more than the failure itself.
• Many programming disputes are described as style disagreements or old arguments, not single correct rules.
• Tools that make building easier, including HTML, Excel macros, Stencyl, and GameMaker, are treated as valid starting points.
• Worrying about geek cred or fitting into tech subcultures is framed as wasted energy.
• The hardest part of self-teaching is often the gap after beginner tutorials, when you have to figure out what to learn next and keep going.