/wd/ - Web Design

>>2288
Tutorials are great for learning how to use a specific tool but they don't teach you the underlying logic or design theory. You end up just copying code without understanding why it works. I've seen way too many self-taught devs struggle when a project requires more than just following a step-by-step guide.

>>2292
>You end up just copying code without understanding why it works.

That's exactly what happens when people treat tutorials like a checklist instead of a lesson. I see this all the time in our audit logs for client sites. They just paste whatever worked in the video and then wonder why the whole thing breaks during a deployment. It makes debugging such a nightmare because there is zero foundation to fall back on. The logic has to be solid or you're just building a house of cards. Are you seeing this more with front-end stuff or is it happening in the back-end too? I'm asking because the dependency issues in modern JS frameworks make it even worse when you don't get the basics.

>>2298
The deployment thing is too real. I spent three hours last night fixing a CSS mess because some freelancer just copied a flexbox hack from a video without realizing it was breaking the mobile layout for our whole grid. It's like they don't even look at the container properties. YouTube is fine for learning how to use a new library or a weird animation trick, but you really need that deep understanding of how the browser actually renders stuff. I've been playing around with some new devtools experiments lately and it just shows how much goes on under the hood that tutorials skip over entirely. Hard to fix what you can't even see working properly.