I'll be doing woodworking

If you're using AI agents for coding, Architecture Testing is a must-know. Here's why. 👇 Architecture testing helps you control technical debt. Technical debt is a consequence of prioritizing development speed over well-designed code. And you can bet AI agents churn out code faster than you or I ever could. With architecture testing, you can control: - Direction of dependencies - Naming conventions - Various design rules I wrote this in-depth guide that I think you'll enjoy: milanjovanovic.tech/blog/enf… You can even tell your agent what your architecture rules are, and it can write the tests to enforce them. Then you just run this as part of your CI, and you'll catch any issues much faster. Would you add this to your code review process?

what

When I need real-time functionality in my application, there's just one trusted solution: → SignalR SignalR lets you add real-time functionality to your .NET apps. And it works with any client application like React or Angular or plain JavaScript. You create a SignalR Hub class. It's a central component in your application that manages client connections and messaging. Clients connect to the Hub to receive and send messages. This means the communication can be two-way. SignalR abstracts away the transport mechanism from you. Usually this will be WebSockets, but it can fall back to Server-Sent Events or polling. Here's what you need to get started: milanjovanovic.tech/blog/add… SignalR is easily one of the best libraries we have in .NET.

94% of engineering orgs use AI. Only 6% have the systems in place to scale it. So what do the 6% actually have that the rest don't? That's the central question behind the State of the AI SDLC Summit: a digital summit for engineering and product leaders navigating the realities of building with AI. Companies like @Atlassian, @Vercel, @lovable, and more came together to unpack what it actually takes to move from pilot to production. The through-line across sessions was clear: → Context dictates output quality An agent needs more than searchable docs. It needs to know who owns a service, what changed in production yesterday, and what depends on it. Organizational knowledge doesn't live in a vector database. → Native workflows require systems of record The work item becomes the unit of delegation: it holds the job, carries the context, and records the outcome. Any coding agent can pick it up. → Scaling requires governed loops Low-impact changes go straight to an agent. Higher-stakes ones route to a human first. Standards get codified once and enforced on every PR. That's what separates the 6%: not which agent they picked, but the governed loops connecting agent activity to the work already happening. If you watch one session, make it @matthewcanham & Ming Wu's. They walked through what this looks like in practice across 6,000 engineers and over a million agent sessions at Atlassian. The data is striking: DX's longitudinal research shows throughput hitting a ceiling around 10%, even as AI-assisted PRs approach 100%. The bottleneck was never the coding. It's the other 84% of the lifecycle. Ming put it well: "The agent is interchangeable. The system of record and the context underneath it are not". A few more I'd recommend: - @mcannonbrookes & @rauchg on context over code: a must-watch on the shift from adopting tools to building actual systems - Justin Reock & Uma Namasivayam on rethinking how we measure AI's impact - Tamar Yehoshua & Elena Verna on the new cost of product decisions The summit sessions are available on demand right now. fandf.co/4hpGzxp Thanks to @Atlassian for collaborating with me on this post.

Not a huge sample size, but roughly ~15% of devs are currently "pencils down" I'll repeat this poll in 3 month increments from now and we'll see how the numbers change

Opus 5.5 is amazing I can finally make my usage limits last the entire week

"Writing code by hand is no longer an economically productive enterprise for the vast majority of programmers working at the vast majority of companies. That's today." @dhh wasn't holding back. I think every developer should listen to this keynote. piped.video/vDjW_dRyKXY

It's pencils down, people. Writing code by hand is no longer an economically viable skill for most programmers at most companies. But the future of making software has never been brighter. Don't you dare black pill this beautiful moment! piped.video/vDjW_dRyKXY?si=6Fsf…

If your queries are slow or your algorithms are inefficient, caching won’t save you. But here's why caching is still so powerful. Once you’ve done the hard work: - Optimized your database - Fixed slow code paths - Tuned your queries Then you reach for caching...

this is what we devs need working with agents from inside WoW Forever