I love the pragmatic place from which you approach it, Akos!
Not sure if you knew the name, but you just described "the Lindy effect". The longer something has survived, the longer it will survive in the future. That's why people with a lot of experience or people with big audiences are expected to last longer than people just starting out.
Rather than going to the extremes of ignoring AI or losing hope we'll maintain our job, we have to adapt and use it as a new tool
I think though that the AI programmer will involve, and the instructions will be at a higher level than the example you gave. There is nothing stopping us from explaining the problem and not asking for microservices - and once we get used to it, the usage will change.
I feel that tools like Devin will level the playing field when it comes to productivity for a developer. But it will also increase competition. The one who can leverage all these tools will have a better chance of success in the long run.
You tackled this in a great way, @Akos . I like that you defined the directions in which AI can really help us as engineers. I think many aspects of the job are time-consuming, repetitive, and more akin to donkey work. If AI software engineers can tackle that, I will jump for joy.
Besides refactoring, prototyping, and testing, as you mentioned, I would also add writing boilerplate code and handling technical debt.
There are many other things that we as humans should focus on, like planning, prioritization, designing, and so on.
There's much more to software engineering than just coding. Coding is really just the tip of the iceberg, as you described it!
I love the pragmatic place from which you approach it, Akos!
Not sure if you knew the name, but you just described "the Lindy effect". The longer something has survived, the longer it will survive in the future. That's why people with a lot of experience or people with big audiences are expected to last longer than people just starting out.
Rather than going to the extremes of ignoring AI or losing hope we'll maintain our job, we have to adapt and use it as a new tool
I loved that overview, fun and to the point :)
I think though that the AI programmer will involve, and the instructions will be at a higher level than the example you gave. There is nothing stopping us from explaining the problem and not asking for microservices - and once we get used to it, the usage will change.
I completely agree on the tests though 🙃
This is a great point of view Akos.
I feel that tools like Devin will level the playing field when it comes to productivity for a developer. But it will also increase competition. The one who can leverage all these tools will have a better chance of success in the long run.
Also, thanks for the mention!
You tackled this in a great way, @Akos . I like that you defined the directions in which AI can really help us as engineers. I think many aspects of the job are time-consuming, repetitive, and more akin to donkey work. If AI software engineers can tackle that, I will jump for joy.
Besides refactoring, prototyping, and testing, as you mentioned, I would also add writing boilerplate code and handling technical debt.
There are many other things that we as humans should focus on, like planning, prioritization, designing, and so on.
There's much more to software engineering than just coding. Coding is really just the tip of the iceberg, as you described it!