I’m Building 100 Tools With AI
Tags: AI | Indie Development | Vibcoding | Open Source
I used to be a backend engineer. Building APIs, setting up services, tuning queues and keeping systems stable. Every project started with careful tradeoffs around architecture, standards and maintainability. Solid, but heavy. Turning an idea into reality used to require a long planning journey.
Now I’ve switched up my workflow: vibcoding. No longer chained to rigid engineering rituals. I don’t wait for everything to be perfect before starting. When an idea pops up, I use AI as my lever and rapidly build a working prototype.
I’ve set myself a wild, fun goal: build 100 tools with AI.
These won’t be polished SaaS products, venture-backed pitches or massive platforms for millions of users. They are small, sharp utilities, each built to solve one tiny, real, annoying pain point: local PDF redaction, batch format conversion, browser automation scripts, lightweight RAG assistants, log organizers, batch processing scripts, data validators, document converters… Some are built for developers, some fix office headaches, and many exist just to solve my own needs.
One hundred sounds like a big number. Break it down, and it becomes approachable: One pain point, one implementation, one release — that counts as one tool.
My years of backend experience are my foundation. I understand concurrency, storage, edge cases and security boundaries. AI is my new multiplier. It shrinks the timeline from idea to working version dramatically. What once took days to prototype can now be validated in hours.
Still, I hold one clear rule: Speed does not mean sloppy work. Tools handling files or sensitive data like redaction run locally whenever possible; your original files never leave your device. Input validation and safety guards stay in place where they matter.
These 100 tools will vary a lot: Some will prove useful and get ongoing iterations. Some are just experimental demos, archived once finished. Others will turn out to be useless once built. And that’s okay. Failed prototypes are part of vibcoding.
All tools will be open-sourced here, with ongoing progress updates. Feel free to try them out, explore and open issues: 👉 https://www.qudo.cc/en/open-source-tools
No overblown promises, no guarantees of perfection. Just keep building.
This is my long-term experiment: A backend engineer, embracing the AI era, forging small tools one after another.
Target: 100. The journey starts now.
come on
ReplyDelete