OVTH / 2026 LIVE · V0.4.0
Ø Overthinking Gateway ↗
Manifesto · Nº 00 · Seven commitments

Why overthinking?
Because the easy answer
usually isn’t.

We are two people in Jakarta writing about AI coding tools the way we wish someone would write about them for us — fast up top, deep underneath, opinionated throughout, and never pretending the magic is magic.

I.
The Seven · What we commit to
001 / 002
Read as
“A contract between us and the tab you haven’t closed.”
Seven numbered. None optional.
  1. I.

    We treat AI tools as craft, not magic.

    The models are impressive. They are also just software — configurable, composable, and often wrong. We write about them the way a carpenter writes about chisels: here is the grip, here is the angle, here is the wood that will split under it. Wonder is fine. Deference is not.

  2. II.

    Flash by default, deep when you ask.

    Every tutorial lands in sixty seconds — the exact commands, copied and pasted, done. Toggle the overthink and the same page unfolds into the full architectural reasoning, the alternatives we rejected, the sharp edges to watch. Shallow as a feature. Depth as a right.

  3. III.

    Opinions are features.

    Neutral comparison tables bury the lead. If we think Claude Code beats Cursor for overnight refactors, we will say so, name the conditions, and show the failure mode. You can disagree. You should. But you will have a position to argue against, not a seventy-cell spreadsheet that quietly recommends whatever sponsored the post.

  4. IV.

    Aggregation wins.

    The future is not one model. It is a router that picks the right brain for the right task — Haiku for triage, Opus for architecture, a local 32B for the offline plane, a reasoning model for the gnarly ones. We build, use, and document the Gateway pattern because lock-in to a single lab is a bet we decline to take.

  5. V.

    Zero vendor lock-in.

    Portable credentials, portable configs, portable minds. Point your SDK at an endpoint you control. When a provider deprecates a model at 3AM we shrug, flip a YAML key, and keep shipping. No single lab owns your stack.

  6. VI.

    Share what works.

    Every config in a tutorial is a config we run. Every copy button copies a line we have actually pasted. The repo is open source because the alternative is performing expertise at an audience instead of handing them something that compiles. Contribute. Fork. Disagree in a PR.

  7. VII.

    Test in public.

    Versions break, prices change, models get smarter and stupider on the same Tuesday. We stamp every page with a last-verified date, re-run the commands against the actual tool, and archive what stopped working. The journal is a living catalogue, not a museum.

II.
Colophon · People · Place · Proof
002 / 002
Colophon · Fig. 02

Built in Jakarta.
Made on Earth.

Edited on a secondhand ThinkPad between coffee shops in Senopati and a desk in Menteng. Typeset in Fraunces and Inter. Code in JetBrains Mono. Reviewed by people who use the tools every day and get annoyed when the docs lie.

There are no sponsors. The Gateway pays the electricity bill. If a tool we cover ever asks for placement we say no and tell you we said no. The journal stays free, fast, and legible on a 3G connection in a warung.

Still reading?

Good. Now go do the thing.

Every manifesto is cheap. The Gateway is the part we had to actually build. Try it free — 500K tokens a month, no card, all models.