About

Hello, I’m Owen. I am fascinated with technology and how it can help enrich people’s lives. I’ve been working on the internet for over 15 years, continuously searching for the best strategies in web performance, security, and user experience.

Badges

Pixel perfection 💎
Pixel perfection 💎
Bright Idea 💡
Bright Idea 💡
Tastemaker
Tastemaker
Tastemaker 10
Tastemaker 10
View all badges

Maker History

  • DebugBundle
    DebugBundleProduction debugging for AI coding agents
  • Sava OS
    Sava OSA desktop interface for your web browser.
    Oct 2024
  • Mastering Web Development
    Mastering Web DevelopmentAn e-book to help you get started in web development
    Feb 2019
  • Buttons
    ButtonsOrganise and share your bookmarks
    Aug 2016
  • 🎉
    Joined Product HuntJune 29th, 2016

Forums

What do you still gather manually before your coding agent can debug a production issue?

I've been building DebugBundle around a simple idea: give a coding agent the evidence it needs in one structured bundle, without making it navigate a complex monitoring setup.

For me, the interesting part is keeping that context simple and useful, rather than just giving the agent more data.

Thinking about the last production issue you investigated with an agent, what did you still have to find yourself? The relevant logs, which version was deployed, a config change, or something else?

I'd genuinely like to hear where you got stuck
I'm in "collecting as much feedback as possible" mode

View more