I just saw a post on Simon Willison’s blog where he linked to “Don’t fall into the anti-AI hype”. And I pretty much agree on what antirez writes there:
Whatever you believe about what the Right Thing should be, you can't control it by refusing what is happening right now. Skipping AI is not going to help you or your career.Don’t fall into the anti-AI hype – <antirez>
Same as Simon writes in his blog, I also see a lot of anti-AI sentiment in the software development community. But same as I wrote in a previous blogpost, these tools can be quite helpfull. But I’m also pretty sure that a lot of people are just using it wrong nowadays, for example by building up huge commits and throw those over to colleagues who should take responsibility. That’s just not the right way.
But just as antirez writes in his last paragraph:
But what was the fire inside you, when you coded till night to see your project working? It was building.
… to me it’s exactly that. In the past couple of years I did less and less private projects because I simply did not have the time. Like “quickly” writing a correct oauth flow (something that I have to do every couple of years) or just things like that which are often just necssary but don’t help me in solving my actual problem have deterred me sometimes in the past.
Nowadays .. this has changed.
It also makes selfhosting so much easier as I can use an assistánt to guide me writing my docker-compose files when I would usually be too tired to concentrate on it.
To me, AI Assitants are a new tool that affects the whole software development lifecycle including team collaboration. And – sure: this is not an easy task! If it’s just used as a tool, decoupled from the process and the team .. yeah well …
Leave a Reply