You're right, but what I want to know are the basics.
To give analogy in software development, I don't want to know how to build an app, I want to know what are the tools to build the app and why.
E.g. use IntelliJ for text editor because it's an IDE (Why IDE is important? Why not Notepad?), use Ngrok for tunnel (why?), use Charles for proxy (why?), use PostgreSQL for DB storing relational data (why? what's relational?), use Redis for caching (why?), etc.. you get the idea.
Yeah, that's what I'm suggesting. Most of the channels I mention (with the exception of Evan and Katelyn) tend to start with a problem, and then walk through the choices made why solving that problem (the "how" and the "why" for each "how").
In my experience, what you're asking about is such a broad space there isn't one "thing" or even category of "things" that apply universally at a fundamental level. Getting good at making stuff is all about building up a broad catalog of options for tackling problems and building up the experience to be able to pick the right technique (or know when the
As an example, I was doing some DIY plumbing over the weekend. We were replacing the flooring in a bathroom in our house and when we removed the toilet we found that not only was the flange that mounts it to the floor totally rusted away, but the plywood on top of the subfloor was in pretty rough shape for a few inches around in every direction. I've never done anything like that before, but by leaning on various techniques I've watched people use in various YouTube videos over the years, I was able to effectively repair it (after calling a friend of mine who does have experience as a plumber to make sure my idea was reasonable).
Probably the most useful technique I used in that project was some approaches to pattern making (since I had to make an oddly shaped "ring" or plywood to fit around the drain) I learned about while watching a YouTube channel about rebuilding a wooden sailboat (https://www.youtube.com/c/SampsonBoatCo). That had nothing to do with plumbing when I watched it, but it was a useful approach that I was able to call upon for a more generalized problem. I think that's what the vast majority of "making stuff" is.
If there are more specific things you have in mind, then there may indeed be specific resources about how to make those things, but it sounded like you were asking a much more general question about making stuff in general.
Are you able to provide some additional context?
1. Can you please provide some links to the videos that you're interested in?
> I want to know what are the tools to build the app and why
2. Are you interested in the fabrication and assembly of something (someone gives you blueprints and you gather and assemble the widget) or are you interested in going from I have an idea to I have a finished product?
3. Do you actually want to build something or just have the knowledge?
To give analogy in software development, I don't want to know how to build an app, I want to know what are the tools to build the app and why.
E.g. use IntelliJ for text editor because it's an IDE (Why IDE is important? Why not Notepad?), use Ngrok for tunnel (why?), use Charles for proxy (why?), use PostgreSQL for DB storing relational data (why? what's relational?), use Redis for caching (why?), etc.. you get the idea.