The rule is simple: Build before you are ready. But in an era where everyone is waiting for the perfect tutorial or the right credential, why does this instinct feel like a rebellion?

Gustavo is in Brazil, building a WhatsApp scheduling SaaS as the CTO of his own startup. 

Irina is in Amsterdam, working as an AI consultant. 

Samuel is in Nigeria, running a home services startup he calls “Uber for repairs” while studying software engineering full time.

Three founders. Three continents. One rule they all figured out independently. Build before you are ready.

The pattern nobody teaches in a lecture hall

Gustavo quit three colleges before he found a way to learn that actually worked for him. “The only way I have ever learned something in my life is from projects,” he says. He shipped an MVP of his WhatsApp scheduling platform, tore it down, and released a full production version in January. Two years of building. Two full rebuilds. One system that now beats his direct competitors on architecture, because they still rely on browser extensions that only work when a window is open. His server keeps sockets alive twenty four hours a day.

Irina was still deep in a machine learning course when she went home one weekend and built an AI agent from scratch to do her grocery shopping. It scraped her local store for weekly discounts and generated her list. Then it got banned from the site. She calls that broken little project her introduction to the whole field of AI agents. “It did not end up working that well,” she says. “But it taught me everything.”

Samuel started building his geolocation feature with almost no backend knowledge. His method was blunt. “Read, read, read. Try. Fail. Try again. Fail again. Eventually it worked.

Why this matters

None of them waited for permission. None of them waited to feel ready. They picked a real problem, took a swing, broke something, and learned. That is not a personality trait. It is a skill, and it is completely learnable.

How AmsterdamTech builds this into you

Our BS in Software Engineering and BS in AI and Machine Learning Engineering are structured around real projects, not multiple choice exams. Students rebuild the hard parts of real products under peer review. They ship. They break things. They learn what a textbook cannot teach, because a textbook does not have production traffic on it at 2am and a real user is not sending you angry messages about a bug in your scheduling logic.

Gustavo, Irina and Samuel all live in different time zones. They all reached the same conclusion. The moment you start building is the moment your career actually begins.

Which project would you start this week if nobody told you that you were not ready yet?