I’ve been writing software professionally for over 25 years. Along the way I spent a few years in product, including a stretch as Head of Product and then as a technical product manager. That part of my career changed how I think about building software. It made me care even more about organization, details, and whether a product actually makes sense when a real person sits down to use it.
These days I’m doing research and development at Wicket, where a lot of my work centers on agentic engineering. I don’t see AI as a threat to good software work. I see it as leverage. The way I work now is shaped by both sides of my background: product and engineering. I like being close to the interface, close to the workflow, and close to the implementation.
That’s also what led to Teex. I built it for my own workflow because I wanted a better review surface for AI-assisted work: a place to read markdown cleanly, inspect code with syntax highlighting, and scan git changes without doing everything inside a terminal or a chat window. It started as something useful for me and turned into the first app under Bucey Labs.
Bucey Labs is simply the home for that work. It’s the banner I’m using for Teex, other developer tools, utilities, and whatever useful products come next.