All video posts

Career · Software development · Entrepreneurship

The 3 Real Ways to Make Money in Tech Today

Late nights on projects, endless tutorials, grinding LeetCode, and it feels like everyone else is doing exactly the same thing. The playbook for making money in tech has changed. It is not about learning every language or building ten to-do apps. Here are the three real paths and how I would approach each.

Deric YeeDeric Yee 16 November 2026 6 min read 7 min video

Prefer to read? The full article is below. Watch on YouTube.

The short version

  1. 1AI is replacing a lot of entry-level coding. The market needs people who solve real business problems, not another login page.
  2. 2Job boards are broken: network and proof matter more than your CV, and specialisation beats generalisation early on.
  3. 3The three paths: a specialised developer, a technical founder, or a tech-adjacent professional.
  4. 4Follow a six-month roadmap: strategy, foundations, a full solution with real users, then positioning.
  5. 5Build systems not just apps, document your process, and build a community around your solution.

The tech landscape has shifted

If you are following advice from a few years ago, some of it still works, but the playbook has changed. Back then AI was not everywhere. Today there are three shifts you need to understand.

First, AI is replacing a lot of entry-level coding. You are not just competing with other junior developers; you are competing with ChatGPT, Copilot and a dozen tools that write code far faster. The market does not need another junior who can build a login page. It needs people who can solve real business problems.

Second, job boards are broken. I run hiring for my companies, and many roles are effectively filled before they are posted. When they are posted, there are a thousand applicants. Your network and your proof matter more than your CV. Third, specialisation beats generalisation, especially for developers early on. I am a fan of being T-shaped, combining skills into specialised knowledge, but I know developers with one year of focused experience in a niche earning more than generalists with five.

Path 1: Become a specialised developer

Forget "full stack" as your whole identity for a moment. Knowing the full stack is good, but it is meaningless unless you are shipping specialised value. Pick a niche: AI integration, payment systems, security, performance optimisation. Companies do not want generalists; they want problems solved.

Think about what you Google most when building apps: login systems, payment flows, notification queues. Be the person who owns that component. Get deep with the real tooling, such as Stripe for payments or Auth0 and Clerk for authentication, and publish open-source wrappers around them. When you specialise and stand out, companies find you.

I have seen this first-hand with career switchers: someone who gets genuinely obsessed with how payment infrastructure works end to end becomes far more interesting to a fintech than a generic junior. Not because they are the best developer overall, but because they understand one valuable thing deeply. If you are weighing directions, our AI engineer vs software engineer guide helps.

Path 2: Become a technical founder

This one is closest to home. I never set out to be a founder. I saw a problem in education, built a small solution, and it became Sigmaschool. You do not have to build the next Facebook. Solve one painful problem for one niche audience.

The best founder ideas often come from your previous life. Someone who ran a small shop knows exactly what inventory headaches look like for businesses like theirs, and can build a simple system for that niche that a generic developer would never think of. Your industry knowledge plus the ability to build is a genuine edge.

This path suits people who love building but hate bureaucracy. Your tech becomes your product. If it appeals to you, read how to build a SaaS with AI for a practical starting point.

“I turned skills into services, services into systems, and systems into a business.”

Deric Yee, in the video

Path 3: Become a tech-adjacent professional

Some people quietly do very well in tech without writing much code: product managers, solutions architects, technical salespeople, AI specialists who design how teams use models. What they have in common is that they solve clarity problems. They take a business problem, talk to developers and get a solution shipped.

That is hard to find and very valuable. Some of the best-paid people I know in tech are former educators, marketers or operations people who learned just enough code to communicate well with technical teams, without becoming specialists. If this sounds like you, see our guide to tech jobs that do not require coding.

How I got here

I was living very lean in Malaysia with no roadmap, just one belief: if I could solve a real problem and get paid for it, I could build something real. I started freelancing, then consulting, then teaching. Along the way I noticed every client wanted better tech hiring, so I built a system to train job-ready developers, which eventually became Sigmaschool.

It did not happen overnight. On every project I asked: what exact pain point am I solving, can I solve it in a scalable, repeatable way, and can I turn it into a system? Skills became services, services became systems and systems became a business. Today I spend most of my time building with AI.

A six-month roadmap from zero

Here is the roadmap I give people who want to go from zero to earning in tech.

01

Month 1: Strategy

Pick your path: specialist, founder or tech-adjacent. Identify one high-value problem you care about and map only the stack you need to solve it.

02

Months 2 to 3: Foundations

Learn the tech by building components, not just finished projects. Build in public on LinkedIn, X or GitHub, join communities and share what you learn.

03

Months 4 to 5: A full solution

Build a complete solution around your problem. Get feedback from real users, then refine the UX, performance and documentation.

04

Month 6: Positioning

Create a landing page and a clean GitHub repo. Reach out to companies with this problem and sell it as a service, a product or your skill set.

What long-term winners do

Tech changes fast, but the people who win long term do three things. They build systems, not just apps: every time they build something, they ask whether it can be reused or refactored into a component, and they collect templates, boilerplates and scripts that speed up future work and collaboration.

They document their process. A good README is a second CV. Notion, GitBook or a thread on X all work. And they build a community around their solution: sharing what they build, talking to users and iterating in public on Discord, Circle or Reddit. People who treat tech as a craft win. People who chase every trend burn out.

This is not about becoming a 10x developer. With AI, everyone can be one, if they know what they are doing. It is about solving real business problems. Pick one problem, get very good at it, and turn the solution into something scalable. If you want structured help building those fundamentals with AI, look at our AI-Native Software Development Programme, or try how we teach first with the free trial.

Questions people ask

  • What is the best way to make money in tech today?

    Focus on solving a specific, valuable business problem rather than collecting general skills. That usually means one of three paths: becoming a developer specialised in a niche like payments, security or AI integration; becoming a technical founder who builds a product for one audience; or becoming a tech-adjacent professional who connects business problems with engineering teams.

  • Should I be a full-stack developer or a specialist?

    Learning the full stack is useful, but early in your career a clear specialisation usually stands out more. Companies hire to solve specific problems, so owning a valuable component, such as payment flows or authentication, makes you easier to find and hire. A T-shaped profile works well: broad enough to work across the stack, deep in one area.

  • Can I work in tech without being a developer?

    Yes. Product managers, solutions architects, technical salespeople and similar roles are valuable because they translate business problems into clear requirements and help teams ship. Many people move into these roles from teaching, marketing or operations. Learning enough code to communicate confidently with engineers gives you a strong advantage in them.

  • How long does it take to start earning from tech skills?

    It varies with your starting point and hours, but a focused six-month plan is a reasonable structure: a month choosing your path and problem, two months on foundations, two months building a full solution with real user feedback, and a month positioning and reaching out to companies. Consistency and building in public matter more than speed.

Your next step

Our 12-week AI-Native Software Development Programme is a live, mentor-reviewed cohort where you build and ship real products with AI, and learn to explain every line. Start with the free trial to see how we teach, then decide.

Watch next

All videos

Learn the fundamentals that pay off in any direction.
Coding plus AI, taught properly.

Whatever you end up doing, the people who understand how software and AI actually work get to direct them. Try the first lessons free, no card needed, or see the full 12-week AI-Native Software Development Programme.