Why I Built ApexDevs

There's a version of this story that sounds inspirational — young educator sees broken system, builds alternative, changes lives.

The real version is messier. ApexDevs started because I kept seeing the same gap: students who had completed four years of engineering couldn't ship a working project. Not a complex one — any project. The education had been entirely theoretical, entirely assessment-driven, entirely divorced from the act of building.

I'd come from the other side: game development, where you iterate, break things, and ship constantly. The gap felt enormous.

So ApexDevs is an attempt to build structured learning paths where the output is a portfolio, not a certificate. Where the measure of progress is "can you build this?" not "did you pass this?"

We're early. There's a lot still to figure out. But the feedback from the first cohort of students was enough to keep going: several got placed in companies they couldn't have accessed otherwise, because they finally had proof of skills rather than proof of attendance.

That's the goal. It'll take a while to get there at scale.