In the present time, it's really hard to stay simple. I have seen many developers using a combination... Tagged with webdev, softwareengineering.

Dev.to is a community platform for developers, offering resources, discussions, and networking opportunities to empower individuals in their coding journey. Developers can learn new programming languages, frameworks, and tools, engage in discussions on best practices, and share their experiences with fellow developers to enhance their skills and grow their professional network.

Developers who rely heavily on frameworks without understanding the basics are referred to as 'frameworkers'. To be a software engineer, one should master the basics and have an understanding of the entire system, not just rely on copying and pasting code. Learning frameworks becomes easier once the fundamentals are solid.

You're not a software engineer; you're a "frameworker"

<blockquote>
We are living in an era where developers know Tailwind but not CSS.
</blockquote>
I think we are ignoring that some of the subdomains in our field have expanded greatly: it’s completely reasonable that someone at the back of the frontend does not have the same mastery of CSS as someone in the front of the frontend- and vice versa, it’s completely reasonable that someone working at the front of the frontend might have mastery of CSS and DOM but be reliant/unknowing of framework-less JavaScript

Great text! Understanding the basics is crucial before using any framework.

I have a counter argument here, the problem is that the market has more demand for frameworkers than software engineers.
Sadly, this problem is more pronounced in senior roles where companies look for someone with more computer science expertise, but they often end up with people who have been using React for years. This is also a result of the unimaginable numbers of tooling and frameworks that are expected of a front-end/full-stack dev nowadays. Often, leading to spreading yourself too thin between a huge number of things to learn that need hours of your time, and aren’t always transferable to newer technologies later on.
In comparison to the backend, where yes it’s harder to get a first job, but the tooling is not that unstable, making the road clearer and naturally pushing you to focus on your basics.
I feel that always blaming the developers for this over and over again is getting old. There are reasons for this current state, and it’s mostly driven by choices of companies and vendors, not the other way around.
The solution? In my opinion, if you’re well off and don’t desperately need a job, choose one domain and one tool only and focus on that.
However, be sure to always focus on the basics and become a true software engineer by saving your time and energy to solving real problems, instead of being a victim of FOMO and internet-induced ADHD.
Focus and time are your greatest resources, be careful as they aren’t renewable.
I give this advice to myself before I give it to anyone else.

I don’t quite agree with this take. I think knowing the basics will certainly give you some advantages in terms of better understanding the framework you’re using, however - in order to understand how a particular framework works, you still need to put in the effort to learn it’s specific syntax, boilerplate code, etc on a fundamental level.
In my humble opinion, it’s not the language, or framework that makes a software developer - it’s all down to the individual’s ability to solve problems using said tools. If you can learn how to learn, and apply it well enough it doesn’t matter if you’re using a framework - or writing everything from scratch yourself.
Additionally, this will be increasingly true as AI copilots and agents enter the development space more and more. Are we going to call people who use these tools not “true software engineers” simply because they’re leveraging things to make their jobs easier? Seems a bit reductionist to me.