About Me

I learned to code at nine with a Pascal book in English and a dictionary missing half its pages. My first program calculated days until summer vacation. It was off by 37 days because I didn't know about leap years. At twelve I copied a hacker website from Geocities so badly I left all their HTML comments in the source for six months. Didn't even know what comments were.

Started freelancing at sixteen. PHP, WordPress, jQuery. Then MooTools before jQuery became dominant. Built a lot of terrible websites for clients who wanted things to "pop more." Learned JavaScript properly when React came out. Spent years doing full-stack work for banks and retailers. Systems that handled money and actual users.

Got into AI in 2015 when TensorFlow dropped. The documentation was basically nonexistent. Stack Overflow had maybe three questions, all unanswered. Took 72 hours to run a single example. Built my first chatbot in 2016. Complete disaster. You'd ask it about the weather and it tried to sell you insurance.

These days I architect AI systems at Atlax 360. Fixing things after the prototype phase ends. Workflow engines that spam users. Document classifiers that label everything as fraud. RAG systems that retrieve everything except what you asked for.

I like seeing exactly what hits the API. More code to write, easier to debug. Abstractions are fine until you need to debug them.

I use AI to write code. Cursor and Claude Code every day. English is not my first language, so I use AI to check my grammar too. My value is in the architecture, not in memorizing syntax.

After 19 years I still break things to see how they fail. My GitHub has repos named 'definitely-not-production' and 'this-might-work-v3-final-final.' The errors just cost more now, and sometimes they're hallucinated by the AI I'm debugging.

Currently interested in context engineering. User state, retrieved docs, conversation history - what goes into the prompt matters more than the prompt. That's where the leverage is.