· Brittany Ellich · illustration · 1 min read
The never ending cycle of maintaining legacy code.
Likes:
Comments:
Social media was supposed to connect us, but most of it has turned into ads, division, and loneliness. I'm betting on ATProto as a way to fix that, and not just for developers. Whether you're a scientist, journalist, or just someone who wants the internet to feel human again, I think ATProto matters for you too.
Nobody knows what the future of software engineering looks like, and that's incredibly uncomfortable. But instead of waiting for someone to hand us the answer, I think the move is to embrace the uncertainty, because these moments of deep uncertainty have historically been moments of extraordinary opportunity.
The best practices for building with AI haven't been written yet, and that's actually exciting. This post breaks down a layered approach to AI-assisted development, from chat to coding agents to agent fleets, with practical tips for getting started no matter where you are.
AI agents like OpenClaw can run continuously on your machine, read your email, push code, and post to the internet on your behalf, often with minimal supervision. I've put together six practical guidelines for using AI Agents without losing control... favor scripts over agents for deterministic tasks, guard against prompt injection, monitor what your agent is actually doing, vet community plugins before installing them, scope permissions tightly, and minimize the data you send. This isn't a "don't use AI" post, it's a "here's how to not shoot yourself in the foot" post.