Should I learn to code?
The short answer
Yes, at a working level — enough to automate, script, and read code. Full career switches are harder than they were in 2015; augment your current work first.
Signals to weigh
- 01You already automate small things — spreadsheets, Zapier, macros.
- 02Your current role has repetitive digital work coding could compress.
- 03You enjoy debugging puzzles, not just the idea of being a coder.
- 04You have 5+ hours a week for 6+ months to reach useful competence.
How to decide
- Step 1Pick one language tied to a real problem you have — Python for data, JS for web.
- Step 2Ship a small useful thing in week two. Not a tutorial — a thing you'd use.
- Step 3Rebuild one workflow at your current job with code. Show the time saved.
- Step 4Decide at month 6 whether to go deeper or park it as a durable skill.
Framework used
Second-Order Thinking →Full walkthrough of the framework, with examples and pitfalls.
Consider these alternatives
- ·Learn SQL and one BI tool if the goal is analysis, not building apps.
- ·Learn to use AI coding assistants well — often 80% of the leverage for 20% of the effort.
Run this decision inside Compass
Get a personalised answer to your version of this question.
Free · Private · Actionable
Begin