ThomIves

I am eager to check this out. Thanks for sharing it!

Building a global postal code API (240+ countries). Just shipped per-country landing pages with format references and regex patterns. $0.000028/query with no tiers, sub-5ms. Bootstrapped, solo.

Building a global postal code API (240+ countries). Just shipped per-country landing pages with format references and regex patterns. $0.000028/query with no tiers, sub-5ms. Bootstrapped, solo.

Nice!

Just read another article about Sylve too. I might have to check it out. I do like PVE, but maybe Sylve would be a step up.

I was very happy to read this one. I do use ProxMox, and I have very few issues with it, but perhaps it would be worth the investigation.

Thank you for posting this. Very good to know!

Thanks for this article. Very important news.

I loved this notion from just the title, and then eagerly read the post. BRAVO! I am investigating if I can, and how to, exploit this ASAP.

The insight that multi-agent coordination is fundamentally a type-checking problem — catch structural failures before spending the compute — is the most practical framing I've seen for this space. The adversarial composition example where information partitioning emerges from types rather than instructions is especially elegant. Looking forward to the follow-up on memory architecture.

With my type of development, I haven't run into the types of things, directly, that you very well explained, but I have personally run into the pain, I confess, of being OVERLY reliant on LLMs. I continue to try and learn from those hard lessons and develop a set of best practices in using AI to help me avoid those pain points in the future. This growing set of best practices is helping me a lot. The reason that I liked your article is because it confirmed some of those best practices that I have had to learn the hard way. Thanks!