Traditional education is often built on a single promise: sit in a chair, listen to a lecture, and you will eventually be ready for the world. But for Gustavo, a software developer and startup CTO, that promise felt like a cage. Before finding a path that worked, Gustavo quit traditional school three times. It wasn’t because he couldn’t learn—it was because he was a “builder” trapped in a system designed for “listeners.”

The “Builder” vs. The Classroom

For many naturally self-taught people, the gap between theory and practice feels like a waste of time. Gustavo always preferred studying documentation and learning by doing. He dreamt of building his own products, not just passing exams.

Coming from a background where he taught himself the basics, the leap into formal software engineering required a complete shift in how he viewed code. He didn’t need a teacher to tell him what to think; he needed a framework that taught him how to build.

The “Failing Forward” Moment

Even for a CTO, the journey wasn’t without its hurdles. When Gustavo first started building his startup—a SaaS WhatsApp scheduling platform—he fell into a common trap. He would start coding immediately without a plan.

This “hacker” approach led to “cracks” in the code, forcing him to rebuild the entire product from scratch multiple times. “I had to change my methods,” Gustavo recalls. He realized that to scale a product for the real world, he had to stop guessing and start creating processes. By moving from “just coding” to “planning and mapping,” he learned to write code once and have it be scalable.

The “Under the Hood” Advantage

What changed for Gustavo at Amsterdam Tech was the shift toward deep, professional fundamentals. While many online courses skip the hard stuff, Gustavo dove into C programming and memory management.

Understanding what happens “under the hood” at a system level changed everything. Instead of just fixing a surface-level bug, he could now identify memory leaks and understand how small, individual processes stack up to create a high-performance product. This technical depth is what allowed him to build a server-side solution that runs 24/7—something most of his competitors struggle to do.

From Solo Coder to CTO

Today, Gustavo’s role has transformed again. He isn’t just writing code; he is managing a team of senior developers. He has moved from the “solo act” of a student to the “orchestra conductor” of a CTO.

He now spends his days planning features, working with UX designers on Figma mockups, and delegating sub-issues to his team. The project-based strategy he practiced in school became the exact blueprint he uses to run his company.

Advice for the Self-Taught

Gustavo’s journey from a school dropout to a successful CTO serves as a reminder that your background isn’t a barrier—it’s an asset. His main takeaway for those who feel “stuck” in traditional learning? Focus on the fundamentals and don’t be afraid to rebuild.

“I’ve always been a self-taught learner,” he says. By finding a program that matched his “build-first” mindset, he was able to turn his passion for products into a production-ready reality.