To get the most use out of Stack Overflow you need to reach escape velocity… meaning you need to be able to know what question you are actually asking and evaluate which of three upvoted answers is the one you need. I have used it a lot.
But it only solves technical issues like libraries and interfaces problems, maybe algorithms or certain language concepts.
You still need to be able to design the thing and know the process for ending up with quality software.
Like the other day when I didn’t receive a package because a part of my address was eaten by the shop software when a backend was trying to fit the address into a database format. Someone writing code for a pretty big shop system apparently had no idea how to evaluate which parts of their application needed how much test coverage… or how to test properly.
The difficult thing is making it efficient and robust and extendable and making sure it is doing what it is supposed to be doing. Figuring out the latter is a whole different rant…