Breaking Into Tech Is Apparently Not Rocket Science. Who Knew?

So many of you want to be able to do cool stuff you see people do, like build websites, games, etc.

But… you’re limited by the idea that it’s incredibly overwhelming and only for intelligent people.

You hear your coursemate say he built a neural network in C back in high school and then think you have no chance of breaking into tech or doing something similar.

While I’m not here to preach AI, I’d have to admit that things have changed a lot since your coursemate was in high school.

The idea was “Who writes better code?” back then. Now, the idea is “Who makes better infrastructural decisions?”

Infrastructural decisions basically mean “What should this software do, and how should it do it?”

That’s it. That’s the developer benchmark for 2026 going forward.

So, if you’re interested in breaking into tech, you have two roads to follow, each preferential.

1. The deep dive path

If you have the time and the courage, you can watch tutorials, learn what you need to learn, then start building things on your own and using AI as your building partner (tool).

This is my preferred approach because I love coding, I love software development, I love everything software, and even a little hardware.

On this path, you’re taking the longer road that’ll require a lot of consistency and patience.

• Start with an overview.
• Then maybe a tutorial.
• From the tutorial, build hands-on things.
• Learn further.
• Build even more on your own.
• Explore AI tooling, etc.

This path is especially for people who want to be “corporate slaves” (just kidding). I meant people who want to be able to apply for jobs in software companies.

You should understand software systems, design, architecture, etc., etc.

1. The vibe path

In this case, you don’t care about coding that much. You don’t care about programming. You don’t care much about the things running your system. You just wanna have that system.

This approach is the more enticing one for most people because you can literally create a full website in 30 minutes, which might take the DEEP DIVE path a week or even weeks.

The main advantage is that you ship fast. The main disadvantage is that you ship fast and you mostly ship garbage (or, as we like to call it… slop).

Maybe you’re a business owner who doesn’t wanna pay a developer $700 for a simple inventory system and feels that you want to build the system yourself. Of course you can!

Vibe coding is a term used to describe aggressive agentic development without knowledge of the code. Or at least interest.

But the thing is… like I mentioned earlier, making a system is one thing. Making a reliable and good system is another thing entirely, and most times, it’s very difficult.

So, how can I vibe code and ensure that I don’t produce slop (note: slop refers to AI garbage that has the tendency to break)?

Easy! You learn just the basics.

Want to build a website? Learn the overview of how websites are built: the frontend, the backend, the databases.

So, you end up being the one to tell the AI what to use and do instead of it telling you.

You aren’t learning programming. You’re learning infrastructure.

Here’s the twist

Now, these two paths are clearly very different, BUT here’s the twist.

Both paths are software engineering (if done well).

YESSSSS! So, what are you actually waiting for?

After reading this, you can absolutely create your first website.

Don’t have a laptop? Search Lovable or v0.dev.

Check materials online for learning, etc.

And if you need any help (completely free), I’m always available.

Now go build something. Or become a corporate slave. Your choice.

And if you get stuck, need learning resources, or just need someone to point you in the right direction, my DMs are open. I help for free, so you have absolutely no excuse.

Reach me on WhatsApp : https://wa.me/shellhakii
Or anywhere @shellhaki