Yes. At least since late '90s, and certainly the last 2 decades.
I blame the rise of frameworks, libraries, and IDEs. It’s easier for someone who knows nothing to throw some software together and ship it. In the good old days, all software had to be written by someone who knew what they were doing, often in difficult tools. You had to think ahead and write code correctly, because you couldn’t just ship patches every week.
And as junior devs get replaced by AI, there won’t be any experience for any of them to learn how to do that.
I blame the rise of frameworks, libraries, and IDEs. It’s easier for someone who knows nothing to throw some software together and ship it.
I very much disagree with this. Yes to an extent you don’t need to know as much as you might have in the past but if we had to constantly reinvent the wheel, I don’t think we would have nearly as many people entering/remaining in this field. Additionally well written frameworks and libraries can actually make your code safer since you don’t have to reinvent the wheel and discover the pitfalls all over again. IDEs are also a net positive IMO. Errors next to the line of code that caused them, breakpoints, interactive debugging. These are all things I personally would find hard to live without. Necessities? Technically no. But good god do I not want to have to read build output unless necessary.
If you can only hobble along with tool support, you never understood what you were doing. You don’t have to rewrite everything from scratch, but if you can’t, you lack the skills to use them effectively, and can’t ever improve on them. And like I say, soon AI will replace those consumers.
Compilers are perfectly able to tell you the line of an error, you can use a debugger without the IDE, I run lldb or the Chez Scheme debugger all the time, but I understand what the tool’s doing.
As long as that growth curve continues there will not be enough teachers, role models, and leaders. It means that most software teams will remain relatively unguided, unsupervised, and inexperienced. […] It means that the industry as a whole will remain dominated by novices, and exist in a state of perpetual immaturity.
Not sure if the data can be confirmed or not, but if that’s the case it will be difficult to maintain the best practices in our industry.
I disagree to some extent. I could never have had a career without Visual Basic and Access. Now in my retirement, I struggle mightily to put together all the pieces required. You might say that getting me out of the field is a good thing, but without masters creating tools and tutorials for journeymen and women, we will forever need the masters on the front lines instead of leveraging their mastery for more valuable ends.
I blame the rise of frameworks, libraries, and IDEs.
My thoughts exactly. Frameworks on top of frameworks with a lot of cruft that will incrementally make software slower and buggy.
That, coupled with the fact that business owners just want things shipped. Quality aside, I dont even think they care about products being good anymore 🥲
Yes. At least since late '90s, and certainly the last 2 decades.
I blame the rise of frameworks, libraries, and IDEs. It’s easier for someone who knows nothing to throw some software together and ship it. In the good old days, all software had to be written by someone who knew what they were doing, often in difficult tools. You had to think ahead and write code correctly, because you couldn’t just ship patches every week.
And as junior devs get replaced by AI, there won’t be any experience for any of them to learn how to do that.
I very much disagree with this. Yes to an extent you don’t need to know as much as you might have in the past but if we had to constantly reinvent the wheel, I don’t think we would have nearly as many people entering/remaining in this field. Additionally well written frameworks and libraries can actually make your code safer since you don’t have to reinvent the wheel and discover the pitfalls all over again. IDEs are also a net positive IMO. Errors next to the line of code that caused them, breakpoints, interactive debugging. These are all things I personally would find hard to live without. Necessities? Technically no. But good god do I not want to have to read build output unless necessary.
If you can only hobble along with tool support, you never understood what you were doing. You don’t have to rewrite everything from scratch, but if you can’t, you lack the skills to use them effectively, and can’t ever improve on them. And like I say, soon AI will replace those consumers.
Compilers are perfectly able to tell you the line of an error, you can use a debugger without the IDE, I run lldb or the Chez Scheme debugger all the time, but I understand what the tool’s doing.
In 2014 Robert Martin claimed that number of developers doubles every 5 years and says:
Not sure if the data can be confirmed or not, but if that’s the case it will be difficult to maintain the best practices in our industry.
I disagree to some extent. I could never have had a career without Visual Basic and Access. Now in my retirement, I struggle mightily to put together all the pieces required. You might say that getting me out of the field is a good thing, but without masters creating tools and tutorials for journeymen and women, we will forever need the masters on the front lines instead of leveraging their mastery for more valuable ends.
My thoughts exactly. Frameworks on top of frameworks with a lot of cruft that will incrementally make software slower and buggy.
That, coupled with the fact that business owners just want things shipped. Quality aside, I dont even think they care about products being good anymore 🥲