Pokemon Go Is Everything Wrong With Lazy Programming
A daily player's teardown of Pokémon GO as a working example of uncreative engineering that shipped anyway and printed money for a decade: a reskin of Ingress, a strategically hollow default battle loop, a gym system that was patched around rather than fixed, and AR that's off by default.
I still play Pokémon GO every day and I've made peace with it "the way you make peace with any relationship built on convenience rather than merit." I use that daily habit as a case study here: the game is less a guilty pleasure and more a working example of what lazy engineering looks like when it ships anyway and keeps working.
Key takeaways
- A reskin of Ingress on the same location database: reuse is smart, but a decade of additions barely touched the core loop (walk, tap, watch a meter fill, unchanged since 2016)
- Default battle loop is strategically shallow: CP is the biggest lever, so you win by over-leveling; GO Battle League is the optional exception
- The gym system was patched around, not fixed: still depends on random player behavior (rural gyms uncontested for months), so the problem just moved
- The headline AR feature is off by default for regular users: a pitch-deck slide that shipped as a toggle
- The lesson: elegant systems aren't what make something succeed; good engineering and successful products are correlated, not the same
Who this is for
Engineers who like arguing about what "well built" actually buys you, and anyone who's shipped the pragmatic-but-hollow version of a feature. Opinion essay, no code, plenty of Pokémon GO in-jokes.
The full teardown is on Substack.