42 Paris
Project-based computer science training across algorithms, systems, networks, and web engineering.
About David
I came through a non-traditional path: self-directed web work, training at 42 Paris, full-stack work in the early 42 Lisboa environment, and several years building in Bitcoin and Web3. Today I apply that operating range to AI systems and technical products.
The short version
Sometimes that means an agent making bounded decisions or a product moving from idea to first users. Other times it is an inscription pipeline operating through a volatile mempool, or a site that must become legible to both people and machines.
Career trace
Each phase changed how I think about reliability, product risk, and shipping.
Project-based computer science training across algorithms, systems, networks, and web engineering.
Full-stack product work across the 42 network and the early operating environment around 42 Lisboa.
Engineering work across Yakuza Inc., Tokentech, and OrdinalsBot, followed by Pizza Ninjas, Pizza Pets, 0N1 Force, and related teams.
Building agent workflows, production software, technical discovery systems, and owned products from Ericeira.
Working principles
Technical judgment is useful when a team understands what it is choosing and what that decision makes harder later.
Automation without review states, failure paths, and ownership is only a faster way to lose control.
A working product, public source, real input, or measurable behavior carries more weight than a polished claim.
The best handoff is not dependency. It is a team that can see how the system works and make the next decision well.
Public profile
The work says more than another biography.