>All of those "things" will be plugged into an AI and one senior technologist will be able to write a detailed functional description of a system in natural lan

>All of those "things" will be plugged into an AI and one senior technologist will be able to write a detailed functional description of a system in natural language I fully agree that this will be possible. However, having worked in the industry, especially FAANG, Ive seen people getting hired and teams grow from 4 devs to 8 solely based on metrics of how long it takes those engineers to finalize projects, and when you look at the work that they do, so much of it is dealing with bullshit friction that doesn't need to be there. One of the most memorable examples was people writing Cloudformation stacks. One of the issues that used to happen is that if you fucked up your template, and the stack started deploying a bunch of infra like EC2 instances, and then it ran into an error, it would take the time to delete all the instances it created, which took forever.I suggested that we just use python+boto3 to define our stacks to avoid this, and people looked at me like I was crazy. So this developer rent-seeking behavior is going to exist for some time thats going to keep jobs in place.