Saw a post from an 8-year dev this week. He said any junior with an agent now matches his output, and he feels no pride left in it. It got huge, because a lot of people quietly feel the same.

I read it from the other side. I'm a designer, not an engineer. For years "can you build this" meant "find someone technical and pray they stay interested." Usually they didn't. AI took the thing that hurt that dev and handed it to me.

Same shift. Loss from one seat, freedom from another.

I'm shipping a Mac app solo right now, as someone who can't write a backend from scratch. Two years ago that was a joke.

Lingo.dev v1.0 introduces localization engines  stateful translation APIs that you configure once and call from backend code, MCP, or CI/CD. Before today, every team that wanted consistent terminology, on-brand tone, and per-locale rules wired it up by hand: a glossary in one repo, brand-voice notes in a Notion doc, prompt scaffolding hard-coded into the app. The engine collapses all of that into a single addressable thing.

What's in the launch

• Localization engines. Configure models, brand voice, instructions, and glossaries per locale.

• LLM models. Pick the model per locale, with ranked fallback chains for reliability.

• Brand voices. Linguistic rules and tone per locale.

• Instructions. Per-locale translation rules for specific patterns.

• Glossaries. Lock down product terminology across languages and builds.

• AI Reviewers. Cross-model evaluation criteria for translation quality.

• Playground. Test engine configurations before they go live.

• Reports. Word generations, token consumption, top locales, glossary coverage, change rates.

I'm gradually seeing how many people in my circles are calling for more capable alternative solutions for products that originally came from the US.

They are switching, for example,

from ChatGPT to Mistral