๐ Simon Willison: Identify, solve, verify
No matter how good these [coding LLMs] get, they will still need someone to find problems for them to solve, define those problems and confirm that they are solved. […] It’s also about 80% of what I do as a software developer already.
Hey, I’m a software developer too. And I acknowledge that my job is more than just typing things into an IDE. In fact, it’s probably closer to what Simon Willison does, where I’m identifying problems, and writing Jira tickets for others to fix rather than do it myself. And it might be that with the introduction of coding LLMs, software development will simply be more of this going forward. It certainly the direction things look to be going.
But I would be lying if I said I wouldn’t be disappointed to see all these coding tasks go away, and all my job description reduced to finding problems and verifying fixes. Like some sort ofโฆ manager ๐. I got into software development because I like to code. And part of this is finding problems, but I only get the dopamine hit after fixing them. I get nothing if I simply tell someone (or something) else to fix it.
And okay, we’re talking about a job here. And I’ve reached the age where I recognise one doesn’t always achieve a fulfilling life from their careers alone. So might be that this is something that I just need to recognise that sometimes jobs suck and identifying problems is all I’ll ever do in the near future.
But I would tell employers thinking of outsourcing all coding tasks to LLMs to consider this: if I’m faced with two employment opportunities, and one has 0% coding tasks, and the other has >0% coding tasks, I’d take the latter any day of the week.