PinnedThe Concurrent Mind·Sep 9, 2025Forget HashMap — These 3 Hidden Java Maps Made My Code 3× FasterMost developers never look past HashMap.A response icon25A response icon25
PinnedThe Concurrent Mind·Aug 16, 2025Big Tech’s AI Gamble Will End in DisasterWrite this down. The clock is already ticking on the biggest write-off of this decade.A response icon17A response icon17
The Concurrent Mind·1d agoYour Ingress-NGINX Is Dead and Unpatched — Replacing Ours Took 13 HoursIt has been almost 8 months since Ingress-NGINX got its last fix. It will never get another one.
The Concurrent Mind·Oct 26Forget MongoDB Sharding — Postgres Partitioning Handled Our 500 Million RowsOur events table crossed million rows, and the plan on the whiteboard was a sharded MongoDB cluster.A response icon2A response icon2
The Concurrent Mind·Oct 24We Replaced 2000 Lines of React With HTMX. Here Is What We Learned2000 lines of React, and the screen did 3 things.
The Concurrent Mind·Oct 22After 5 Years, We Finally Stopped Using ModelMapper — CPU Dropped 60%For 5 years, one line of code ran on almost every request we served, and none of us thought about it.A response icon1A response icon1
The Concurrent Mind·Oct 20We Removed Reflection From a Java Hot Path — and Cut p99 Latency by 85%The code was not complicated. That was part of the problem.
The Concurrent Mind·Oct 19AI Can Write the Code. Senior Engineers Still Own the FailuresLast Thursday, an AI tool wrote 14 lines of Java that looked perfect at first glance — every line neatly formatted, the code compiled on…A response icon2A response icon2
The Concurrent Mind·Oct 18I Tested 7 PostgreSQL Optimization Tricks. The Most Popular One Made Everything WorseSeven fixes, one table, ten million rows. The advice everyone repeats was the only one that made it worse.A response icon1A response icon1
The Concurrent Mind·Oct 17We Cut Database Queries by 80%. The API Was Still Slow.The dashboard said we had won. The users said nothing had changed. The users were right.A response icon2A response icon2
