15 Years Writing C++ - Advice for new programmers

Main ideas / concepts

• Personal background & perspective

  • The speaker, Chris, has 15 years of programming experience with C++.
  • He works professionally in game development, using C++ daily.
  • He keeps old code files out of habit/paranoia that he may need them later; this video is prompted by finding an early C++ file dated June 23, 2008.

• Response to common advice about C++

  • Chris notes that many people online tell new programmers not to learn C++, claiming it’s:
    • problematic,
    • old,
    • likely to frustrate beginners into quitting programming.
  • He agrees C++ has problems (no language is perfect), but argues that beginners shouldn’t be deterred.

• What beginners should focus on

  • Beginners don’t need to worry much about:
    • whether their chosen language will still matter later,
    • “doing it the right way” from day one.
  • The key focus is learning by doing, such as:
    • writing code,
    • experimenting by changing/mutating files or behavior,
    • encountering errors and learning to debug.

• Lesson about perfectionism

  • Chris reflects that earlier in his learning he became overly focused on:
    • whether he was learning “the right way,”
    • copying how respected programmers learned.
  • He believes this mindset caused him to spend less time programming and avoid practicing enough.
  • He argues that writing “bad code” more often and learning to identify why it’s bad would have helped him and saved time.

• Overall encouragement / takeaway

  • There’s no “end of the world” scenario for programming learning.
  • If someone is interested and thinks they might enjoy it, the solution is simple: start writing code immediately.

Methodology / instructions presented

• Start learning by direct practice

  • Open your IDE of choice.
  • Write code right away.

• Focus on building and experimentation rather than “right way”

  • Don’t overthink perfect methodology.
  • Aim to get things running and interacting with the changes you make.

• Use mistakes as learning

  • Expect errors.
  • Learn how to debug when things break.

• Don’t obsess about long-term language relevance

  • You don’t need to worry that the language you choose now won’t matter a year later.

• Avoid perfectionism-driven avoidance

  • Don’t delay programming because you fear writing code “wrong” forever.
  • Practice often—even with imperfect (“bad”) code—so you learn what “bad” looks like and how to fix it.

Speakers / sources featured

• Chris (speaker/host; 15 years programming experience, C++ game developer, talking about learning advice)