Software-Development

Trigger warning: this is part rant, part genuine exploration, and entirely my opinion. As usual. Also; research heavy. I wanted this to be informed. I’ve been thinking about this one for a while. In a previous post I argued that not everyone who writes code is an engineer, and that the title carries expectations. In another I complained about the lack of standards in an industry that rewards speed and hype over depth. And more recently I got on my soapbox about fundamentals mattering — about how the people who actually understood the machines they worked on are slowly dying off, and what we’re being left with instead. ...

🤔 The thing about how much AI agents and tools have improved is that I’m finding myself in a weird spot. I’m always working. Even when I’m not working, I’m planning and brainstorming in Claude Projects so I can use the spec and plan files later in Claude Code. In a recent interview with The Pragmatic Engineer, Mitchell Hashimoto, the founder of HashiCorp said his “new rule for building software: always have an agent running in the background doing something.” (link) ...

🤖 I love how every new LLM release triggers a wave of “AI is coming for your job!” posts, only for people to realize a few weeks later “oh, nope, sorry, not this yet” 😏 💡 While AI tools are certainly force multipliers for productivity, even with agents, they’re not replacing humans yet. Even the best apps I’ve generated with Bolt or Replit eventually need human intervention and fixing. 🎯 Hot take incoming: I find it amusing when people consider these simplistic example AI-generated “apps” as “real development”. Most modern webapps are already essentially just careful combinations of frameworks and styling, using existing tools that solve problems in generic ways. That’s not novel software development. ...