>>107048625 (OP)
>HTML/CSS/TailWind/JS/SQL/Python/C# stack
not trying to sound rude but it sounds like you just googled "full stack languages" and just took the first 7 you saw. just pick your favourite back-end language and a front-end framework and learn those. you can learn tailwind or any CSS framework later
JS itself is not that hard. it has a lot of warts, which is to be expected from an old web technology. unfortunately that's just something you have to deal with. typescript makes it slightly better but not by much. eloquent javascript is a good book if you want to learn the fundamentals (
https://eloquentjavascript.net/ )
the problem is in the ecosystem. generally you have two main targets: browsers and servers. if you're writing server code, you need to use some js runtime, typically node.js. it's usually pretty simple, it just works. if you're building a front-end application, it's a lot fucking dumber. between shit like bundlers (webpack/parcel/vite), transpilation (babel), your chosen front-end framework (let's be real, nobody is working with the DOM API by hand in 2025), CSS preprocessors, NPM, linting, and whatever other shit you need, it can turn into a nightmare real fucking quick. luckily most frameworks nowadays come with scaffolding tools to generate project templates for you, but if you're working on anything non-trivial you'll quickly realise just how fucked modern front-end development can be
by the way if you don't already know git you should prioritise learning that as well