I guess a lot of people are afraid of being left behind.
What goes into the average developer's day? I think a lot of time is spent writing boilerplate, fighting with tiny CI errors, shuffling code, refactoring, writing tests and staring at code hunting bugs. As this technology matures, all of that noise might go away, and I think a lot of people are having a hard time imagining what they are left with.
Remember, we were trained in the "classical" fashion. How will budding engineers approach learning in 10 or even 50 years?
This resonates. I’ve noticed my work goes in cycles. Part of a cycle is the actual implementation (where all this boilerplate work resides). I can’t wait until this mindless work is no longer a burden and I have free cycles to do more interesting things.
What goes into the average developer's day? I think a lot of time is spent writing boilerplate, fighting with tiny CI errors, shuffling code, refactoring, writing tests and staring at code hunting bugs. As this technology matures, all of that noise might go away, and I think a lot of people are having a hard time imagining what they are left with.
Remember, we were trained in the "classical" fashion. How will budding engineers approach learning in 10 or even 50 years?