Nikolas Dimitroulakis

This post is meant to reach exactly 7.7 million people. Not more. The global developer population: around 47.2 million. Assume about half actually work with APIs as a real part of their job, not just occasionally. So we go down to 23.5 million. Of those, maybe a third are the ones actually testing and debugging APIs regularly, not just calling one endpoint someone else wrote and hoping it works. We are now at ~7.8 million. Add QA and test engineers: there are a bit over 1.2 million of them worldwide, and a real chunk of that job is exactly this: hitting endpoints, watching things fail, figuring out why it broke between environments. Call it ~700K who work with APIs specifically. Total so far: ~8.5 million people on Earth doing real, ongoing API work. Now let's be honest and shave a slice off the top. There's a devoted minority who will never leave Postman, the curl purists who don't want a tool at all, and others building everything from scratch out of pure stubbornness. Call it 10%, roughly 850K people. Respect to them. They're not who I'm talking to. That leaves ~7.7 million. If you're not in that group, genuinely, no offense, this post is not for you. If you are in that group: hi. I know you. You are the one still maintaining a Postman collection with 400 requests and a naming convention only you understand. Still chasing an auth failure that only happens sometimes. Still got an environment variable that's wrong in exactly one teammate's setup and nobody knows why. APIs have never been more automated and less visible. They get generated, tested, deployed, all without anyone really looking at them anymore. The work didn't disappear. It just stopped being seen. So to my 7.7 million: we're building @VoidenMD for exactly this. A tool that adapts to how you actually work, instead of forcing you into someone else's workflow. Everything's open, in plain text, so nothing's locked away in a proprietary format you can't touch. You compose what you need, request by request, instead of fighting a rigid template. It runs offline, because your work shouldn't depend on someone else's server. And it's built for a world where AI is writing and running requests alongside you, not bolted on as an afterthought. Welcome home. Population: 7.7 million. We'll update the sign.

From 12 January 2027, the EU Data Act stops cloud providers charging you to switch away, including egress fees to move your data out. The exit bill goes away. The work stays: everything built on one provider's own services. If leaving were free, would you move anything? #EU #cloud

Yesterday GET /orders returned 3 items. After today's deploy: 200 and an empty list. What did it return yesterday? Nobody saved it. In @VoidenMD , turn on request history and each response is kept locally: body, headers, status, timing. Copy the old one as cURL for the bug report. docs.voiden.md/docs/core-fea… #DevTools

Every feature flag is an if statement you promised to delete. One for a launch. One for a single customer. One "just in case". A year later there are 140 and nobody knows which ones are still on in prod. Do you have a rule for removing flags, or do they live forever? #SaaS #webdev

Open source dev tool founders: what was the first signal that people were really using it? A) GitHub stars B) Issues opened by strangers C) A pull request from someone you've never talked to D) Someone writing about it without being asked #OpenSource #BuildInPublic

An API test fails 1 run in 20. Nobody can reproduce it. What does your team do? A) rerun CI and merge B) skip it and open a ticket C) stop and fix it first D) delete it, it was flaky anyway #Testing #CICD