I wrote a small tool for myself as my biannual
routine check of where llms are currently at. I think I've learned a bunch from this exercise. This
is frustrating! I don't want to learn by trial and error, I'd rather read someone's blog post with
lessons learned. Sadly, most of the writing on the topic that percolates to me tends to be
high-level --- easy to nod along while reading, but hard to extract actionable lessons. So this is
what I want to do here, list specific tricks learned.

Matthias Noback's expertise in PHP and domain-driven design (DDD) offers readers  insights into building maintainable and domain-focused software. Through his blog and publications, Noback shares practical advice on software architecture, clean code principles, and effective communication within development teams. Readers can learn how to apply DDD principles to PHP projects and improve the overall design and quality of their software systems.

matklad

A developer shares practical lessons learned from building a VS Code terminal editor extension using Claude AI. Key insights include using a plan.md workflow for structured LLM interactions, treating specs/code/tests as interchangeable formats, and the critical importance of fast, end-to-end testing for AI-assisted development. The author emphasizes that while LLMs excel at code generation, they require proper feedback loops and human oversight in the control plane rather than data plane.

Vibe Coding Terminal Editor

<p>Some similarities with the warp terminal</p>
