An honest reality check

What a switch really takes in time, money and effort, what the entry-level market looks like now, and why some switches stall.

Also called timeline

What: The realistic time from starting to learn to a first paid tech role. For people studying part time around a job, one to two years is common; full time with strong focus can be shorter, but rarely a few weeks.
Why: A realistic timeline lets you plan money, family time and checkpoints. Expecting three months leads to panic, rushed paid courses and quitting at month four.
Example: At 10 hours a week, 600 hours of learning and projects takes about 14 months. At 20 hours a week it takes about 7 months, before any time spent applying.

Watch out

Trusting advert timelines such as "job-ready in 12 weeks" that assume full-time study and ignore the search.

Also called junior job market, entry-level market

What: The supply and demand for junior tech roles in your city or remote market. Since 2023 many markets have had fewer junior openings and more applicants per role, while AI tools changed what junior work looks like.
Why: It sets how strong your proof must be and how long a search may take. A harder market does not mean no chance; it means a generic profile gets filtered out faster.

Watch out

Judging the market from viral posts in either direction instead of counting real junior postings where you live.

Also called opportunity cost, full cost, cost of switching

What: Everything a switch costs: course fees, a laptop and internet, exam fees, and the biggest one, the income and time you give up while learning or taking a lower first salary.
Why: Counting the full cost stops a switch from turning into debt or family stress, and it shows why free learning first is almost always the right order.
Example: A free curriculum plus a working laptop costs little in money, but 12 months at 12 hours a week is about 600 hours taken from rest, family or overtime.

What: The common reasons people give up: no clear target role, jumping between courses, never building anything original, never talking to anyone in the industry, and quitting a job before savings or skills were ready.
Why: Most of these causes are about plan and habits rather than talent. Knowing them early lets you design against them from the first week.

Watch out

Believing you failed because you are "not a tech person" when the real cause was an unfocused plan.

What: The loop of finishing one course or video series after another while feeling unable to build anything alone.
Why: Following along feels like progress but trains recognition, not recall. Building something small without a guide is what makes skills stick and creates proof.
Example: After each course section, build a tiny variation without the video: a different form, a different dataset, a different page.

Watch out

Starting a second beginner course because the first "did not explain enough" instead of building with what you have.

What: The situations where a degree is still required or strongly preferred: some large employers and government or bank roles, graduate programmes, many work visas abroad, and research or specialist roles.
Why: Knowing where a degree matters tells you which doors to aim at first and whether a formal qualification is worth adding later.

Watch out

Assuming "no degree needed" is true everywhere, then targeting employers and countries whose rules filter you out.

Also called coffee chat

What: A short, low-pressure conversation with someone already doing the role you are considering, to learn what the work is really like. You ask about their day, not for a job.
Why: Two or three chats before you commit can save months on a role you would not enjoy, and they start the network you will need later.
Example: "I am a teacher considering technical writing. Could I ask you three questions about your work, for 15 minutes, whenever suits you?"

Go deeper