Blog posts other developers make detailing the way they've built a particular project have helped me gain some perspective when looking to understand how people are working in a particular stack. Learning from other projects is good for understanding how people are using contemporary tools. Github is also a great source for this, you can search with those tags to find relevant projects. As for software engineering in general, there is more academic materials which cover various methodologies ( you can just search software engineering and find many resources ). There are so many resources out there; I don't personally have a systematic way of navigating it. Once I find a good resource, I tend to look at what else the author has done and who else is connected to that author and then I walk around what that social circle's body of work, picking up various things. Finding the sages in a particular area, finding out who really knows about the area I'm studying at the moment, then learning from them... all starting from Google searches and some sleuthing.
Blog posts other developers make detailing the way they've built a particular project
The hard part is finding the right blog. There are a ton of blogs out there from developers with little experience who are convinced that their way of doing things is the best/only/right way. The blogs are often nothing more than SEO for their resumes.
For that reason, I'd lean heavier on books. At least with books there is some filter. Yes, it can be incomplete and sporadic, but it's often better than the wild west of bad information out there, especially in web dev blogs.
Yes, good point. Usually you can filter blogs by reading the comments and seeing the reception it got as well as the popularity. If it is an open source project, you can see the stars on GH and read through the issues on the repo to further filter. Books get outdated very quickly for modern tech stacks. I would recommend them for the fundamentals, but not contemporary stuff. You obviously have to do your due diligence here. Researching the author is also important obviously if you are going to truly heed their advice.
