Alejandro Teixeira

Projects

About

I like simple systems that scale: clear meaning, explicit interfaces, and boring reliability.

I started extremely early: at around 2 years old I was already typing game loaders on a Sinclair Spectrum because my father taught me. I learned a bit of BASIC, and later (around 9–10 years old) a school initiative got us programming in class. In between, I also tinkered with an old Amstrad PCW. Later, at ~12, I was gifted another old Amstrad (this time with a mouse), and by ~14 I got my first proper PC: a Packard Bell with an 850MB hard drive and 8MB of RAM. That’s when early internet arrived in Spain — and Linux followed soon after.

I studied Physics for two years, then moved fully into programming and started working in the industry. That’s where I picked up most of the breadth: languages, systems, and the real constraints of scaling technology in production.

Over time I became more interested in architecture — in the deeper sense: how tiny choices (a single line of code, a formatting decision, even the order of an if) can save “millions” when technology scales. They compound into fewer incidents and claims, simpler systems, faster time-to-market, fewer errors, and lower compute/operational costs. That perspective naturally pulled me toward what we now call CI/CD; later: containers, Scrum, and microservices.

After years working in the industry, an idea started forming in my head — and for more than a decade I couldn’t quite give it a concrete shape. The core was simple: unify components by cataloging what things do (their capabilities), so software can be built modularly with meaning preserved. With the recent AI wave, it suddenly clicked: the tooling is finally here to make that approach practical. That’s how the idea turned into OKHAM.

Today, I’m fully focused on OKHAM.

Contact

Links (more coming soon).