Hi PH, I'm Mase, I built self-healing code because I was too anxious to go camping
Hello everyone!
I'm a self-taught dev and former fuel salesman (yes, really). I started coding about 4 years ago, working evenings and weekends with a couple of friends on a project called Settl. We ran it for 3 years and managed to exit.
After that, I went back to my day job selling fuel and realized ZoomInfo was almost useless for fuel sales. So I built FuelScout: a fuel-specific lead gen tool. Everything was going great until I onboarded my first paying customer.
That's when it hit me: I'm a solo dev. If my customer faces a bug while I'm camping, fishing, or on holiday, nobody else is there to fix it. I started getting anxious about customer churn every time I stepped away from my laptop.
So I built an internal tool. It ingests and analyzes production errors, gathers context from my codebase, writes a minimal fix, runs my test suite, and pushes the change to production. I set up auto-deploy on commit.
Then I went on holiday with my wife's family for a week. When I got back, I checked my tool, a fix had been auto-deployed while I was gone. I hadn't touched a thing.
I knew immediately that other devs would want this. So I went to work productizing it.
Today that little tool is called BugStack. It supports JavaScript, TypeScript, Ruby, Go, and Python. It's already live with a small but loyal group of devs using it in production.
I come from the B2B sales world, so building in public is brand new territory for me. I'm genuinely torn on something and would love this community's input:
Do I launch now while the product is solid and working? Or do I spend more time in this community first, supporting other makers and building relationships before going for it?
Either way, my vision for BugStack is simple: nobody should have to fix runtime errors ever again. Just focus on building.
If you're a dev, I'm curious: what would make you trust an automated tool to push code to your repo? Trust is the thing I think about most.
If you've launched on PH before, what's the one piece of advice you'd give a first-timer?
And if you're building something too, drop it below. I'd love to check it out.
— Mase
Replies
This is a really clever idea! Hats off to you, would I use it?
A production push while I'm away sounds kinda scary, potentially if it gave me a review message with this is the bug - this is the fix, approve / deny / fallback options, I would definitely consider it.
Regarding launch or wait, I can't say for sure as I haven't launched my first product yet, but one thing I will say is my iPhone notes contains 517+ business ideas and I regret not starting sooner and going full steam ahead with just one great idea, and time is precious - so take from that what you will. I would love to try out BugStack someday, so I'm keeping my eyes peeled for the launch. 🚀
bugstack
vibecoder.date
Would I trust it?
If it works for my application yes, I'd test it and try to find the limits.
Launch advice:
Your value prop has to be obvious, dead simple conceptually.
Launch now or later?
A lot of launches benefit from already loyal followings outside of here, but I can't say definitively if that is required.
bugstack