Optimising your memory allocations in Java could make far more difference than your choice of Garbage Collector, and may even change which garbage collector is best. Chronicle FIX already persists each message; what if we use SLF4J/logback to write another copy
blog.vanillajava.blog/2026/06/why-...
I am all in on AI writing 20K LOC a day.
I use it for mock systems, quick prototypes, and sample use cases. It works well enough, but it's not worth reading, usually not worth adding as test cases, and certainly not worth using in production.
www.linkedin.com/posts/peterl...
The problem isn't technical; inefficient use of AI is expensive. My team uses Claude and Codex nearly every day, and I have generated ~1M LOC this year.
Yet AI accounts for ~1% of our costs, and I don't think spending much more would help.
www.linkedin.com/posts/peterl...
AI^2: writing scripts and plugins so that AI prompts are programmatically produced and monitored.
Your CLI AI is running other AIs and monitoring those.
The widespread use of AI has led to expectations for best-of-breed solutions that far exceed productivity gains, meaning major tasks can take much longer.
www.linkedin.com/feed/update/...
The biggest benefit of AI is that it serves as a rapid-learning tool to broaden your knowledge. It can help close gaps in your knowledge up to average levels with relatively little effort
www.linkedin.com/posts/peterl...
I don't just expect AI to fail regularly; if they don't, I make the problem harder.
www.linkedin.com/feed/update/...
For those old enough to remember the Iraq/Afghanistan wars, with about 93 million people in them combined, they cost ~$8 trillion in today's money.
Iran also has 93 million people, and the war there could cost the same over the next 20 years.
Sureal moment: I told Codex the way /prompt worked wasn't right, and now it's looking through the ~/.nvm Codex code to figure out why