FWIW, I have professionally held the title of Full-Stack developer for over 5 years, and kind of hate the title now due to the presumptions and expectations others have for full-stack folks. So much stress.

I'm glad I did it, it expanded my horizons and I know where my strengths and weaknesses are.

More importantly, I have experienced enough to appreciate and respect the role of the backend developer and collaborate better.

As a developer of 20 years, teacher of a college dev class, and even a manager who sadly hired a few developers that shirked the basics: you WILL shoot yourself in the foot later if you try to jump to frameworks like Django without fully understanding the core basics first. I know it, because I did so myself, and watched so many new developers do it. 😛

Successful developers need a balance of curiosity and patience. Yes, absolutely explore Django on your own time, but don't dismiss the class! You'll better understand and appreciate the pros AND cons of frameworks if you already know the core language.

Besides, it's rare that a client will want functionality straight out of the box from a framework. You will be expected to build or customize something from scratch eventually.

I've sifted through enough resumes that name-dropped frameworks to make my head spin, but when interviewed, could not answer basic core language problems without frameworks as a crutch. Don't be like them!

@AlgoRythm 🤣🤣🤣

@theabbie lol, thank you. Someone actually gave a reason of some kind. 😆

@ScriptCoded Interesting -- I'd love an example if you have one. I didn't know that was a thing.

@010001111 I have. And sure, I can see the difference, but only because I'm actively looking for it. And because I have a design background and an eye trained for that.

Our users, for the most part, do not look for this, nor are most of them trained in visual design. They don't care if the edges are slightly notched or not.

Too real! 🤣