Everyone needs their own tools now
AI is making building more accessible. The interesting question is no longer which app everyone should use. It's what to build around the way you actually work.
Something is changing about how people relate to their tools.
The internet is full of people sharing workflows now. Prompts, skills, agents, MCP setups, vibe coding patterns, tiny automations, full personal systems. The raw material for building is everywhere and it is getting cheaper to use.
Building is becoming accessible.
That changes the question.
For years the question was: which tool should I use? There was a finite set of options, adoption had friction, and most people settled on whatever the team or industry standard was. The leverage was in choosing well.
The better question now is: what should I build around the way I actually live and work?
That shift sounds small. It is not.
Most tools are designed for the median user. They make reasonable guesses about how work flows, what needs to be remembered, what handoffs look like, what a publishing rhythm should be. For a lot of people, reasonable guesses are good enough.
But your capture habits are not generic. Your publishing voice is not generic. Your projects, your memory patterns, the way you move between thinking and doing. None of that is generic. And a tool built for the median will always grind against the edges of how you actually work.
When building is hard, you accept that friction. When building becomes easier, you start to notice it.
This is the thinking behind TheBalaOS. Not a clone of one tool or one framework. A personal operating system built around the way I actually work.
- Markdown and Git as the source of truth, because plain files survive tool changes.
- Astro for the public site, because it renders fast and stays out of the way.
- Studio for carousels, because the rendering is its own job.
- Agents for repeatable judgment: research, editing, critiquing, publishing, packaged as skills with clear handoffs.
- Automations for capture and routing, running quietly in the background.
Different jobs deserve different tools. The system is designed so that when a better tool appears, it can be swapped in without rebuilding everything.
That last part matters most.
In the AI era, migrations feel less like cliffs and more like chores. If the data is plain, the interfaces are clear, and the pieces are small. An agent can help rewrite the glue when the stack changes. The condition is keeping the system modular enough that there is actually a glue layer to rewrite, rather than one monolith that owns everything.
The real idea here is not that every person should build their own tools. It is that more people can now than before, and for people who work in ways that do not fit the standard shape, that option is worth taking seriously.
Your personal operating system should be modular.
Not because frameworks are bad.
Because your life is not a framework.