📰 Dev.to · TABATA Hitoshi

Eight of my eighteen AWS scanners failed against a fake AWS — and that was the point

pg_total_relation_size() takes a lock. My locks page waited behind the lock it was there to explain.

pg_cancel_backend() returned true. The queue didn't move.

I deleted a queue and my own CLI told me a resource had been added

My drift detector cried wolf every time my autoscaler scaled out — and the fix was a tag AWS already sets

My infra tool could show drift, grade it, and Slack it — but it still couldn't fail a CI build

A '12 libraries to make your Python production-ready' list crossed my feed — I use 2 of them, because a framework already made the other 10 decisions

Your connection pool is exhausted. pg_stat_activity tells you which of the three causes it is.