It's so interesting to me as a Mechanical Engineer and Hardware designer/architect how on HN "Engineering" almost always means "Software engineering" here.
edit: typo
To answer the OP, this Civil engineering blog / video site is really good. I always learn something new, and his enthusiasm is infectious. Well worth giving it a look:
In general, though, my very limited experience working in manufacturing was that much of the blog equivalents were covered in things like white papers from hardware manufacturers or articles in trade publications. We always had a bunch of magazines delivered each month and there were usually some interesting articles to review.
Maybe, generously, in retrospect, an aspiration?
I never considered myself an actual engineer; I was (and still am) a self-taught un-credentialed computer programmer. More art than science. They made me take the title and the stock options and the business cards.
I mostly worked for and with EEs, making software tools for test automation. I was a fanboy hardware wannabee (and still am), got some on me but was never a true engineer. I learned from those who practiced their discipline; it was plain to me the reality of real engineering versus what I was doing.
I suppose in my travels I have on occasion encountered a true Software Engineer. I suppose there's reason to hope that software development will continue to mature and evolve, and eventually the other engineering disciplines will accept software as a science.
For me, it will always be a joy to make that hardware work with my twiddly bits. Not engineering, no. But very rewarding work that often resembles engineering.
but to specific is much important, imo Engineering means "Solving problem at a scale", irrelevant of the industry.
Words change meaning over time and with the audience.