Programming

Long-term maintainability: This is the most insidious impact radius because it has the longest feedback loop, these issues might only be caught weeks and months later. These are the types of cases where the code will work fine for now, but will be harder to change in the future. Unfortunately, it’s also the category where my 20+ years of programming experience mattered the most.

Article covering all the ways an expert engineering had to guide AI, out of pitfalls, away from landmines and most importantly towards a long-term sustainable architecture. If AI is truly a Jr Engineer, code quality will regress (GitClear research on AI depresses code quality)

Through a combination of static code analysis tools (such as CodeQL), fuzzing the GRUB2 emulator (grub-emu) with AFL++, manual code analysis, and using Microsoft Security Copilot, we have uncovered several vulnerabilities. … Copilot identified multiple security issues, which we refined further by requesting Copilot to identify and provide the five most pressing of these issues. In our manual review of the five identified issues, we found three were false positives, one was not exploitable, and the remaining issue, which warranted our attention and further investigation, was an integer overflow vulnerability.

The thing I’m most excited about in our weird new AI-enhanced reality is the way it allows me to be more ambitious with my projects. As an experienced developer, ChatGPT (and GitHub Copilot) save me an enormous amount of “figuring things out” time.

I think the key is in the expertise. As noted in other blogs AI generated code is the dopamine sugar rush of our time. Just because its sweet doesn’t mean its right. Trust Simon and his expertise, but he’s still publishing Python code.

I’m 4 days into an afternoon project … Like Icarus, my codebase is irrecoverable. A tangled heap of wing fragments and melted wax, dripping with half-baked ideas and unsupervised AI chaos. My grand vision of outsourcing grunt work to AI had sent me soaring, but the sun of reality burned away any hope of landing gracefully.

I feel you nemo. This silly little micro blog I thought I could whip up with AI (the api gateway portion). But alas it took me fragmented hours over several weeks before I finally understood enough to accomplish what I want.

I am increasingly distressed by the race to replace human developers, particularly the more junior ones, with AI assistants. … Companies are jumping on AI as a way of removing those messy (and expensive) humans from the process of developing software.

I think the best observation is that “people don’t know what they want”. If AI Coding is the proverbial horse, then everyone wants a faster horse; no one will ask for the car. Most research I find and post here indicates a 10-20% overall productivity improvement, but really as Dave points out that efficiency will be filled with more ambitious work.

When I got stuck with a problem, I had two options: PRINT commands and a lot of dedication, or back to the library. Debugging at that time meant: running, hitting an error, searching, adjusting, and running again with fingers crossed. But in my view, this is just the next step in a long evolution of developer tools.

Eclipse, Firebase, and Stack Overflow haven’t replaced developers, and AI won’t make us obsolete either. Instead, it creates some space for what really matters in software development: creativity, innovation, understanding what the customer wants, and solving complex problems. You could even say that productivity doesn’t increase, but expectations do. … AI functioned as a private tutor who could communicate exactly at my level.

It’s like a wood chipper fueled by dollars. It can power through shockingly impressive tasks, using nothing but chat. You don’t even select context. You just open your heart and your wallet, and Claude Code takes the wheel. It even helps keep you in the loop by prompting you every eight seconds to ask if it can use basic read-only commands that you would allow anyone, even North Korean hackers, to run on your machine.

SA: I mean, my basic assumption is that each software engineer will just do much, much more for a while. And then at some point, yeah, maybe we do need less software engineers.

Lots of ink spilled on the nature of software engineering. I find it hard to believe that we’ll need fewer engineers… but flaged this as a ‘prediction’ so I can check back later.

_{Quote Citation: Ben Thompson, “An Interview with OpenAI CEO Sam Altman About Building a Consumer Tech Company”, March 20, 2025, https://stratechery.com/2025/an-interview-with-openai-ceo-sam-altman-about-building-a-consumer-tech-company/}

As coding becomes easier, more people should code, not fewer!

Oft repeated, AI won’t take your job, but someone using it probably will.

_{Quote Citation: Andrew, “DeepSeek-R1 Uncensored, QwQ-32B Puts Reasoning in Smaller Model, and more…”, March 12, 2025, https://www.deeplearning.ai/the-batch/issue-292/}