Bodhisatta Bhattacharjee
Full-Stack & Game Developer · GlitchBong
I build small, free tools for the problems I keep hitting myself, and I put them on the internet in case they are your problems too. No accounts, no trials, no usage meters, and nothing that quietly uploads your data so it can be sold back to you as a feature.
What I build
GlitchBong is where the finished things live. There are 5 of them right now, and they came out of the same place: I wanted something specific, the free version of it had a row limit or a sign-up wall, and writing it turned out to be less annoying than paying for it.
- Query Studio — Free SQL translator, formatter & validator
- Git Rescue — Git cheat sheet & fix-it playbook
- Storage Inspector — Chrome Web Store extension — see every byte a site stores
- Table Grabber — Convert any table to CSV, Excel, Markdown, JSON, SQL and more
- Grande Verse — an unofficial ariana grande fan site
Two of them ship as Chrome extensions on the Web Store. Both install with no site access at all and read a page only when you invoke them, which is a deliberate choice rather than an oversight: an extension that asks for permission to read every site you visit is asking for a great deal more than it needs to copy a table.
Why the tools are free, and why there is no AI in them
Every result Query Studio produces is computed by real SQL parsers and rule engines, not by a language model. That is not a purity position — it is what makes the tool free, instant, unmetered and, most importantly, the same every time you run it. There is no per-request cost to pass on, so there is no reason to put a limit on it. A translator that gives you a slightly different answer on Tuesday is not a translator.
The same reasoning runs through the rest. Git Rescue is 56 hand-written recovery guides and 82 documented commands, and each guide says up front whether your work can actually be recovered — including the cases where the honest answer is that it cannot. Query Studio covers 18 dialects. Nothing here is a demo of something else you are supposed to buy.
Games
Before the tools there were games, and there still are. They are built in Unity, they run in the browser with nothing to install, and they are the reason this site exists at all — the tools grew out of the tooling I kept writing to make the games. You can play them here. The Git guide on resolving Unity scene and prefab merge conflicts is not a hypothetical.
Writing
I write up the things that cost me a weekend, on the theory that they cost somebody else one too. Architecture decisions, bugs with a real diagnosis rather than a workaround, and the occasional postmortem where the conclusion is that I was wrong about something for three months. The blog is here, and there is an RSS feed if you would rather not check.
Elsewhere
Source for most of this is public. If something here is wrong, broken, or missing an obvious case, telling me is genuinely welcome — the contact page is the fastest route.