From interfaces to systems

People ask for the short version of what I do. The honest version is longer than a title and shorter than a résumé. I build software, I work with the people who build it, and I keep trying to make the day around that work less noisy.

The screen was the apprenticeship

I learned by making interfaces. Not as decoration. As the place where a product either keeps its promise or leaks it. A button that does not say what happens next, a form that punishes a mistake, a page that looks finished and feels lost — those are engineering problems wearing a visual coat.

That apprenticeship still governs how I look at AI. If a model writes the first draft and the interface gives a person no way to see doubt, edit the result, or know where a claim came from, the screen has failed. The model is not the product. The decision the person can make is the product.

Leadership showed the rest of the system

Leading made a different layer visible. The code was never the whole job. Reviews, planning, hiring conversations, and the tone of a hard week decide what a team is willing to attempt. A clever workflow that only one person understands is not a system. It is a private trick.

I care about useful systems, careful engineering, and humane leadership. Those are not three brands. They are the same standard applied to a pull request, a meeting, and a Tuesday afternoon. If a practice needs hype to sound valuable, it is probably not ready.

The best use of a new tool is the one you can explain to the person who has to live with the result.

AI is a material

I use AI where it shortens a repetitive pass: shaping a first draft, listing edge cases, comparing two approaches, turning a messy note into a checklist I can edit. I do not hand it the judgment. Taste, accountability, and the context that never made it into the prompt stay with the person.

That is why this site is not a consultancy brochure and DeepAIOS is not presented as a finished platform. DeepProgrammer is the public notebook. DeepAIOS is the initiative growing out of it: workflows, resources, and workshops, named clearly, shipped only when there is something real to hand someone.

What this site is for

Build, Lead, and Live are the three drawers. Technical notes go in the first. Team and career judgment go in the second. Attention, tools, and the shape of a working day go in the third. Some weeks one drawer is empty. That is better than filling it with a performance.

• I publish generalized lessons, not confidential work.
• I label prototypes as prototypes.
• I would rather show a small workflow I still use than a diagram of a system I cannot stand behind.