I have never been very good at staying in a single lane.
My background runs from neuroscience and ethology to full stack engineering, DevOps, AR/VR, and applied AI. That mix is not a branding trick, it is simply how my brain works: I like complex systems, moving parts, and the places where disciplines collide.
In practice, I design and build systems that have to think a bit, not just respond. I am comfortable moving from Python or JavaScript into C#/C++, from cloud infra to immersive interfaces, and stitching everything together into something that can be shipped and maintained. I care a lot about determinism, observability, and making sure that "intelligent" software can actually be debugged when it misbehaves.
On the side, I am building OrKa as an open source project to validate my approach to cognitive reasoning architecture. OrKa is my personal lab for modular cognition: agent graphs instead of one big prompt, explicit memory layers, and deterministic orchestration of LLMs and tools. It is how I explore questions like "how should a reasoning system route, remember, and explain itself" without being limited by a single product roadmap.
If you are interested in modular AI systems, local and hybrid deployments, or just better ways to reason with software, I am always happy to connect and compare notes.
