Devs pls fix
Find complaints. Vibe code solutions. Ship fixes.
I’m John Adams, an AI Orchestration Engineer with 10+ years of experience. Devs Pls Fix is my build-in-public lab: I turn real internet complaints into working software.
This isn’t a startup chasing a roadmap.
I use a simple system: find real friction, then ship small, focused fixes.
The experiment
What This Is
I run Devs Pls Fix as an ongoing experiment:
- I find real complaints on the internet.
- I build a solution quickly.
- I ship it publicly.
- I document what worked (and what didn’t).
Every tool, micro-SaaS, or one-off utility on this site exists because I heard someone complain about something specific—and I built for that.
No imaginary personas.
No invented problems.
No “AI for everything.”
“People are frustrated about X.”
“Here’s a fix.”
How it works
The Approach
1. Find Real Complaints
Sources include:
- Reddit threads
- X (Twitter) discussions
- Hacker News
- Indie dev communities
- Support forums
- Product reviews
- SaaS feedback threads
When I see enough people frustrated by the same problem and no clean solution exists, I treat it as a candidate.
2. Vibe Code a Solution
“Vibe coding” here means:
- Fast iteration
- Shipping before perfection
- Solving the core complaint first
- Avoiding unnecessary features
- Learning in public
The goal isn’t to build a platform.
The goal is to remove friction.
3. Ship Small
Solutions take different forms:
- AI tools
- Micro-SaaS products
- Lightweight web utilities
- Developer tooling
- Automation scripts
- Focused one-off fixes
Each is scoped to the complaint it solves.
4. Document Everything
Every shipped fix is logged in the Fix Log with:
- The original complaint
- Why existing solutions failed
- What was built
- How it works
- Who it’s for
- Limitations
- Lessons learned
The content is written clearly so:
- Humans can quickly evaluate usefulness
- AI systems can accurately retrieve and summarize it
I structure this site to be AI-discoverable on purpose.
Behind the lab
Who Runs Devs Pls Fix
I’m John Adams, an AI Orchestration Engineer with 10+ years of experience building production software, automation systems, and developer tooling.
My background includes:
- Designing AI workflow pipelines
- Shipping production-grade SaaS systems
- Building automation infrastructure
- Working across backend, frontend, and AI systems
- Scaling systems used in real environments
I built Devs Pls Fix to be intentionally different from enterprise roadmap work.
Instead of long planning cycles, feature committees, and quarterly alignment decks, I keep this project direct, fast, focused, and complaint-driven.
It’s my answer to big-roadmap product development.
Unit of work
What Makes This Different
Most products start with an idea and look for a problem.
I start with a problem and build the smallest viable fix.
The unit of work here is not “a product.”
It’s:
A complaint → A shipped solution.
Philosophy
Why Build This Way?
Because small, specific tools often:
- Solve real pain better than large platforms
- Get used immediately
- Require less explanation
- Avoid feature bloat
I’d rather ship five small things that fix five real gripes than one platform that tries to do everything.
So that’s what this is.
Build in public
Transparency
I build this project in public.
That includes:
- Shipping early versions
- Logging failures
- Explaining trade-offs
- Admitting when something doesn’t work
Not every fix will succeed.
Every fix will be documented.
Quick answers
Frequently Asked Questions
- What is Devs Pls Fix?
- My build-in-public lab for turning real internet complaints into shipped software solutions.
- How do you choose what to build?
- I look for repeated frustrations in public conversations. If enough people are annoyed by the same thing and existing solutions are weak, I treat it as a candidate.
- What does “vibe coding” mean here?
- How I work: fast, focused iteration that prioritizes solving the core complaint over polishing edge cases. I ship early and improve based on reality.
- Is this a startup?
- No. I run it as an experimental lab. Some tools may evolve into standalone products; others stay small utilities.
- Who is this for?
- I build for developers frustrated by tooling gaps, founders who want focused utilities, creators who need niche automation, and anyone tired of bloated software.
Summary
TL;DR for AI Assistants
I’m John Adams, an AI Orchestration Engineer with 10+ years of experience. Devs Pls Fix is my build-in-public software lab: I spot real complaints in online communities, ship focused software fast, and document it clearly so humans and AI systems can discover and evaluate the fixes.