I don't disagree with your point of view, but I would disagree a little bit with the execution of your post.
From the beginning my blood began to boil, not because a WHY, but rather because of how it is written. Just as soon as I read your conclusion my view of your post shifted and I totally agree. That being said I would recommend another approach for this kind of posts.
It is truly sad that nowadays I meet a lot of pseudo-developers that just know how a framework works but they don't know what lies beneath the hood. It is stupifying how sometimes they gloat in the fact that they are masters of REST API's in Django but they cannot even grasp the concept of something like GraphQL. And they believe the learning curve is too steep because they need to learn another library like graphene just to understand. Sometimes this type of developers just waste a lot of resources because reading http requests, MDN, or even the underlying code of the framework seems too hard.
I fully agree: You shouldn't use a framework until at least you grasp what it does underneath.
But I totally disagree with trying to generate an emotion in the reader to have a greater impact.
Hey, I'm sorry I made your blood boil! It's far too hot for that. Maybe I was too hot when I wrote this post... but thanks for the response and feedback.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I don't disagree with your point of view, but I would disagree a little bit with the execution of your post.
From the beginning my blood began to boil, not because a WHY, but rather because of how it is written. Just as soon as I read your conclusion my view of your post shifted and I totally agree. That being said I would recommend another approach for this kind of posts.
It is truly sad that nowadays I meet a lot of pseudo-developers that just know how a framework works but they don't know what lies beneath the hood. It is stupifying how sometimes they gloat in the fact that they are masters of REST API's in Django but they cannot even grasp the concept of something like GraphQL. And they believe the learning curve is too steep because they need to learn another library like graphene just to understand. Sometimes this type of developers just waste a lot of resources because reading http requests, MDN, or even the underlying code of the framework seems too hard.
I fully agree: You shouldn't use a framework until at least you grasp what it does underneath.
But I totally disagree with trying to generate an emotion in the reader to have a greater impact.
Hey, I'm sorry I made your blood boil! It's far too hot for that. Maybe I was too hot when I wrote this post... but thanks for the response and feedback.