For building small to medium new projects with unfamiliar languages, stacks, and tools, this absolutely makes sense. On the other hand, I’ve struggled to get much value out of copilots when working on existing, medium to large, mature (ish) codebases, on stacks etc that I’m already familiar with. Copilots may be good at generating small, self contained blocks of new code, but they don’t really help at all with changes that touch a handful of places across an existing codebase in nontrivial ways. Still makes me feel conflicted that I’m not using the hot new thing though!  

Bridgy Fed’s bridging has been down some today. Apologies, all! I’m on vacation with limited access right now, so the downtime has been longer than it would be otherwise. I’m working on it as best I can. Not sure if it will be back up soon or tomorrow, but I’ll keep you posted.

It’s been a month since the last Bridgy Fed status update, so it’s time for a new one! I’ve spent a lot of time over the last month on user-visible improvements and bug fixes, notably more complex post types and links, as well as underlying infrastructure. Details below. Continue reading →

Finally got around to reading Geoff Huston’s comprehensive, heartbreaking eulogy for DNSSEC. He takes the thought-provoking position that TLS has largely subsumed the need for DNSSEC – not perfectly, and with a somewhat different threat model, but still. Great networking neckbeard reading, as always.

My daughter just informed me that my name is now Carl. 🤔

🤪