Should you actually learn to code?

Everybody tells students to learn coding. Almost nobody tells them honestly whether they should. Here's an honest attempt.

When the answer is probably no

• You want a business, sales, HR or operations career and coding just sounds impressive
• You're learning it out of fear rather than interest
• You'd be doing it instead of getting genuinely excellent at Excel, communication or your actual field

Being outstanding at spreadsheets and clear writing will do more for a business career than three months of half-learned Python. There's no shame in that; it's just where the leverage is.

When the answer is probably yes

• You enjoyed the tea-making exercise more than you expected
• You want to work in data, analytics, product, or anything technical
• You find yourself doing the same thing 200 times and thinking "there must be a better way"
• You're curious. Genuine curiosity survives the frustrating parts; ambition alone usually doesn't.

The honest middle path: learn a little

There's a genuinely useful middle position most people never consider. Two to three weeks of Python is enough to:

• Read and modify code someone else wrote
• Automate small repetitive tasks in your own job
• Check whether an AI-generated script is sensible
• Talk to developers as a colleague rather than a customer

That's a very high return for a very small investment, and it stops well short of "become a programmer".

What to learn first, in order

1. Python. It reads almost like English. Free courses everywhere. Use it for automating files, spreadsheets and reports.

2. SQL. Frequently more useful than Python for office work, and much smaller. SQL asks questions of a database:

SELECT city, SUM(amount)
FROM orders
WHERE order_date >= '2025-01-01'
GROUP BY city
ORDER BY SUM(amount) DESC;

Read it as English: "give me each city and its total order amount, this year only, biggest first." Two weeks of SQL makes you the person who can answer data questions without waiting for anyone.

3. Then decide. If you've enjoyed Python and SQL, go further — web development or data analysis. If you haven't, stop. You already got the useful part.

How to learn without giving up

Most beginners quit in week three, always for the same reasons.

1. 1Build something you actually want. Not exercises. A script that renames your photos, or totals your expenses. Motivation comes from usefulness.
2. 2Expect it to break constantly. Errors are the job, not a sign you're bad at it. Professionals stare at error messages all day.
3. 3Type the examples out. Reading code feels productive and teaches you almost nothing. Your hands need to make the mistakes.
4. 420 minutes daily beats 4 hours on Sunday. Programming is a language; languages need frequency.
5. 5Use AI as a tutor, not a ghostwriter. Ask "why doesn't this work?" and "explain this line". Don't paste code you can't read — you'll feel fast and learn nothing.