4 ms·
Okay. I've been developing software for 40 years now. Frameworks became a thing a little over 30 years ago. Industry productivity soared - so much so that that
by taylodl 1y ago
Okay. I've been developing software for 40 years now. Frameworks became a thing a little over 30 years ago. Industry productivity soared - so much so that that was our last big productivity boost in the industry.
There are a myriad of other benefits from using frameworks, so many in fact that to me it's a red flag when someone advocates against them.
With regards to AI, like I said in my original comment it's a tool, not a panacea. Experienced software tradesmen are learning how to effectively wield AI - hint: it's not for writing all your code. I'm kind of excited because we could be on the verge of another great productivity boost like we experienced 30 years ago when we adopted frameworks.
- austin-cheney 1y agoThe biggest red flag I have against frameworks is that its a leaky abstraction that induces human insecurity. I have been doing this a very long time and it always comes up. Always. People cannot architect because they expect this to be a solved problem. People cannot execute outside what the framework provides, because they are deathly afraid of writing original code. People can't measure things because they have no reason to once they are locked into their framework conventions. Every decision point becomes a defensive game reasoned around the idea of "I can't*. That is the primary reason I wanted to change employment from writing JavaScript to something else. If I could find JavaScript employment without this insanity then maybe I will reconsider my options. I see AI as more of the same.