The worst part of this kind of thing is that young carpenters honestly, really, truly, just need to learn to use a hammer. They can't even conceive of the problems that are being solved by the hammer factory, let alone the factory factory. But in the world of the factory factory factory, the apprentice carpenter (who really just wanted to drive a few nails) is now faced with trying to understand the gargantuan comple…
Everyone needs to learn to do calculus by hand before advancing to the calculator. People picking up frameworks without fundamental understanding is a shockingly common fallacy.
Why I Hate Frameworks (2005)
51–60 of 407 posts
Re: Why I Hate Frameworks (2005)
#52Re: Why I Hate Frameworks (2005)
#53Earlier quoted context omitted.
I mean, you certainly should learn arithmetic before using a calculator, right? But a calculator is more of a library than a framework, anyway, so your attempt at proof-by-analogy isn't at all resonating with me. (edit: I think I misread the comment I replied to and am now in the process of maybe figuring that out downthread.)
Calculators do a lot more than arithmetic these days. Without knowledge of calculus, most people think of a calculator as a magic “black box” that outputs square roots and cosines.
I frankly still can't tell as that's use of "fallacy" to describe "people picking up frameworks without fundamental understanding" is apparently extremely confusing to me as it isn't in the form of a fallacy--like, is the fallacy that this happens? that this is a problem? is it the thought which leads people to do that? etc.--so I automatically added stuff to the sentence to make it work and maybe I did it wrong.
Re: Why I Hate Frameworks (2005)
#54Earlier quoted context omitted.
Everyone needs to learn to do calculus by hand before advancing to the calculator. People picking up frameworks without fundamental understanding is a shockingly common fallacy.
Wait, you're saying that calculators now do symbolic differentiation and integration (like sympy and mathematica)? Kids today...
Re: Why I Hate Frameworks (2005)
#55I remember following up the Angular tutorial. I was about 15min into the tutorial, and I was already editing 8 different files. I never got lost so quickly. I lost a job because I could not use angular, but never felt bad about it. I remember somebody commenting here on HN about a developer conference, where the speakers were bragging about their software being complex. This is an awful trend with software, and is re…
Re: Why I Hate Frameworks (2005)
#56Simplicity is easy to mandate: "just use simple tools!". It's not always obvious when the finished product looks wonky and slanted and has to be retrofitted several times that the complexity was always there, in the world. The complexity in our tools is hopefully there to help with some complexity in the world. In my experience, it's always the junior who shouts "This could all be so much simpler!".
> In my experience, it's always the junior who shouts "This could all be so much simpler!". Yeah, this is true. But I often wonder how much of this is because the seniors have given up on simplicity and since they have internalized the complexity it doesn't bother them anymore.
Re: Why I Hate Frameworks (2005)
#57The counter point to this is that the purpose of frameworks is to turn O(N) problems into O(k) problems by implementing a seam in the code.
The problem a framework ultimately solves is that some teams will choose to use screws, some will use a hammer and nails, some will use a nail gun, some will use glue, some will carve connecting joints, some will use metal and weld, some will take a large piece of material and carve it out, etc. etc. and now you have 50 different ways to perform one task, which is to get the end result of joining two objects.
That means 50 different on-boarding processes, and 50 different design paradigms to manage, 50 different classes of corner cases, 50 different monitoring/operational paradigms, 50 different hiring processes, etc. etc.
Sometime between 50-500 engineers it becomes necessary to properly framework-ize the unit of business logic that product developers work on, like a route, to prevent operational overload.
Re: Why I Hate Frameworks (2005)
#58Earlier quoted context omitted.
I mean, you certainly should learn arithmetic before using a calculator, right? But a calculator is more of a library than a framework, anyway, so your attempt at proof-by-analogy isn't at all resonating with me. (edit: I think I misread the comment I replied to and am now in the process of maybe figuring that out downthread.)
Calculators do a lot more than arithmetic these days. Without knowledge of calculus, most people think of a calculator as a magic “black box” that outputs square roots and cosines.
Re: Why I Hate Frameworks (2005)
#59Re: Why I Hate Frameworks (2005)
#60I do take the point but I feel like the era of the factory factory was a while ago and I'm almost nostalgic for it compared to the dubious soup that we seem to have to deal with now.
dubioussoup.ai Edit: I donno why, but the concept of dubious soup has me CRACKING UP right now.
The ever growing field of prompt engineering continues to grow.