Brutally Honest Advice For Someone Trying to Learn To Code

Key Wellness, Self-Care, and Productivity Takeaways (Brutally Honest Advice for Learning to Code)

Expect discomfort—and stop looking for reassurance

• There isn’t a “perfect course” or mentor that will remove the hard part.
• The “hard part” isn’t access to information—it’s tolerating the discomfort of being bad at something new.

Swap “no time” for a short, non-negotiable sit-down session

• Claiming you’re too busy is often avoidance, not scheduling.
• If scrolling/Netflix feels easier, your brain is choosing what feels good right now.
• Strategy: dedicate 20–60 minutes and stop negotiating with starting.

Stop consuming coding content as a substitute for practice

• Watching tutorials and “roadmap” videos can create an emotional sense of progress without building skill.
• Strategy:
  • Treat content as optional support, not the main activity.
  • Prioritize writing code over watching people talk about coding.

Build evidence, not an identity

• Employers/clients don’t hire “effort” or “trying hard”—they hire evidence.
• Strategy: shift from saying “I’m learning” to showing what you built.

You may not be underqualified—you may be under-evidenced

• A lot of people lack demonstrable outputs (finished projects, clickable links, real work), even if they’re capable.
• Strategy: focus on producing work others can evaluate.

Unfinished projects don’t just get ignored—they’re “worth nothing”

• The unfinished portion (tidying, edge cases, deploying) is where much of the learning happens.
• Strategy:
  • Finish one thing badly rather than starting many things brilliantly but abandoning them.
  • Aim to complete the last 20% instead of avoiding it.

Reduce decision paralysis: pick a path and start

• Spending weeks deciding what to learn is time not spent learning.
• Strategy:
  • Pick one today and move on quickly—even if you might be “wrong.”
  • Don’t let “research” feel like progress.

Own your code (especially if you use AI)

• If you can’t explain your own code, you don’t truly “own” the learning.
• AI can help, but beginners shouldn’t rely on it to do work they can’t reproduce.
• Strategy:
  • Use AI, but ensure you can write and explain the result.
  • For beginners: write by hand before leaning on AI outputs.

Don’t expect outcomes just because you tried

• Effort alone doesn’t guarantee results; the market doesn’t reward how hard you worked.
• Strategy:
  • Focus on solving problems others pay for.
  • Increase visibility—being findable matters.

Stop relying on job portals alone

• Submitting to crowded portals is described as the least effective approach.
• Strategy:
  • Build something for a real business.
  • Talk to the actual decision-makers (including in person).

Treat coding like a priority, not a hobby (if you want a career outcome)

• If you want job-level changes (salary/circumstances), protect time for it.
• Strategy:
  • Make it a primary commitment, not leftover time.
  • Accept that “hobby results” come from “hobby time.”

Consistency beats cleverness; feeling “stupid” is normal

• Feeling stupid won’t disappear—it comes and goes like weather.
• The main differentiator is consistent practice + finishing + putting yourself in front of real people.
• Strategy:
  • Don’t quit near the point where things start to click.
  • Track progress through outputs and completion, not confidence.

---

Presenters / Sources

• Iman (speaker; creator promoting a one-on-one coding boot camp and free course)