The reasoning

Why this exists

Two honest reasons. The first is that I wanted to roast IT people in public. The second is more useful: personality in software is the thing that always gets cut. A team means to give an app a bit of tone, then the deadline arrives and the humour ends up as a handful of hardcoded strings scattered through the codebase, never quite consistent and impossible to reuse. SnarkAPI is that tone pulled out into one place you can call.

So it does exactly one thing: a single GET returns a single fresh insult. No key, no quota, no onboarding call to discuss your needs. A bot, a build script or a bored developer can all reach it the same way and get back a plain line ready to pipe.

The joke is the surface; the point is underneath. SnarkAPI is a portfolio piece that happens to be funny, built on the same clean-architecture discipline as the serious work: ports, adapters and a proper service layer, so even the sarcasm respects the dependency direction. It is proof that a gag can be engineered rather than thrown together, which is a more convincing demonstration than a straight-faced example of the same shape.

What works now is a live FastAPI service at snarkapi.com behind a landing page that types its verdict at you over a moody blue downpour. Open source under GPL-3.0, no feelings spared and the drama is not a bug.

Full reasoning at crankthecode.com.