The SIMPLEST Way to Become Good at Coding

Summary

Phillip Choi argues that becoming good at coding depends less on consuming tutorials and more on actively solving problems. During a coding boot camp, he watched lessons and copied code but continued to struggle. He eventually realized that passive study felt boring because it did not require him to reason through problems. Learning became more engaging and effective when he started investigating errors, testing small changes, and asking what the code expected.

He describes this shift from “spectator” to “detective” as the foundation of his progress. Over time, he went from being one of the least confident students to helping classmates and finding a path into professional software work. On the job, he learned to tackle unfamiliar parts of a system rather than staying within comfortable areas.

Choi also emphasizes connecting learning to practical needs and real consequences. He expanded beyond front-end development because he wanted to build complete products independently. Later, while working on a mental-health journaling app and leading development for a social network with about 250,000 users, he saw how reliability, testing, and sound technical decisions could affect real people. He presents responsibility and meaningful work as motivation to persist through frustration and tedious tasks.

On AI, Choi says coding knowledge is still important: AI can reveal whether someone truly understands what they are building. Engineers can use AI to learn and work more effectively, but relying on generated code without understanding it risks creating fragile, messy systems. He sees building a complete product—from design through debugging and shipping—as a valuable way to learn.

Practical Method and Advice

• Choose one technology stack instead of trying to learn several at once.
• Build one real project that addresses a problem in your life, or recreate an existing product and keep adding features until it becomes your own.
• Work through problems actively:
  • Inspect errors instead of immediately turning to another tutorial.
  • Ask what changed, what the code expects, and what assumptions you may be making.
  • Test the smallest possible change, observe the result, and keep iterating.
  • Treat confusion as a signal to investigate, not as proof that you lack ability.
• Learn what the work requires, not only what feels comfortable. Follow how data moves through a system, identify its source of truth, consider failure cases, and investigate what you do not yet understand.
• Use AI as a learning aid, not a substitute for understanding. Ask it to explain errors, quiz you, critique code, or suggest approaches; do not blindly copy its output.
• Persist through the messy stages. Debugging, testing, edge cases, and trade-offs are part of building, even when they are frustrating or unexciting.
• Keep building until problem-solving becomes familiar. The goal is not just to study coding, but to become someone who can make and ship things.

Speaker and Source

• Phillip Choi — the sole speaker, sharing personal experiences and advice.