Should I learn to code because of AI?

Only if you want the kind of day coding gives you. AI has made writing code easier and made judging, specifying and building around it more valuable. Test a small build before committing to a bootcamp.

How do I choose between data, product and engineering?

Compare the days, not the salaries. Spend an hour finding a pattern in a real spreadsheet, an hour writing what a small feature should do and why, and an hour making something work. One of those hours will be noticeably shorter than the others.

Is it too late to switch direction?

Almost never, and the experience you already have is usually the advantage rather than the sunk cost. Combining a field you know with a new direction is a stronger position than starting a new field from zero.

Do I have to choose something technical at all?

No. Plenty of durable directions are about people, judgement, craft or physical work. The method is the same: test the day before you commit to the training.

Before the course · 7 min read

Should I learn coding, data, product, or something else?

The choice between coding, data, product, design or something outside tech is usually made too early and too abstractly. Here is how to decide it with two weeks of evidence instead of six months of a course.

Written by the OffLadder editorial team · Last reviewed 29 August 2026 · Sources listed at the foot of this page

The short answer

Don't pick the subject, pick the direction you want to test, then let the subject follow. Coding, data, product and design are not really competing skills, they are competing kinds of day: precise building, patterns and evidence, deciding what gets made, or how it feels to use. Do a short real version of two of those days this week and you will know which one you want more of. Only then choose a course, because a course is an excellent second step and an expensive way to explore.

You are choosing between days, not subjects

Coding: long stretches of precise building, small wins, a lot of things not working at first.
Data: sitting with messy evidence until it says something, then persuading people of it.
Product: deciding what should exist, holding several conflicting needs, writing more than you expect.
Design: how a thing feels to use, iterating on detail, showing work to people early.
Something else entirely: teaching, trades, care, operations, making physical things. Same method applies.

A two-week comparison

01Week one: pick the two directions you are most curious about. Do a one-hour real task in each, not a tutorial.
02Write two sentences per hour. Which minutes went fastest, and what you would fix if you did it again.
03Week two: give the winner three hours and take the losing one off the table for now.
04Now choose the course, if you still want one. It has a direction to serve.

A course is a good answer to a question you have already tested.

The reason this order matters is money and time. Six months into the wrong programme is a hard thing to walk away from, and people stay for the sunk cost rather than the work. Two hours is easy to walk away from, which is exactly why it produces honest answers.

Questions people ask

Should I learn to code because of AI?: Only if you want the kind of day coding gives you. AI has made writing code easier and made judging, specifying and building around it more valuable. Test a small build before committing to a bootcamp.
How do I choose between data, product and engineering?: Compare the days, not the salaries. Spend an hour finding a pattern in a real spreadsheet, an hour writing what a small feature should do and why, and an hour making something work. One of those hours will be noticeably shorter than the others.
Is it too late to switch direction?: Almost never, and the experience you already have is usually the advantage rather than the sunk cost. Combining a field you know with a new direction is a stronger position than starting a new field from zero.
Do I have to choose something technical at all?: No. Plenty of durable directions are about people, judgement, craft or physical work. The method is the same: test the day before you commit to the training.

Sources

Future of Jobs Report 2025 · World Economic Forum
LinkedIn Economic Graph research · LinkedIn

How this page is written

We only state what can be checked. Where a page makes a claim about work, automation or the labour market, it links to a primary source rather than paraphrasing a secondary summary. We do not publish predictions dressed as facts, invented statistics, or lists of AI-proof jobs. Pages are reviewed and dated when the argument or the underlying evidence changes. More about OffLadder.