How can I think more like an engineer?

Think about the pros/cons and their costs and impact is 99% of the engineering work.

It is also why the overwhelming majority of software is terrible and IT departments are plagued by inefficient low performing teams: there's no engineering nor real thinking. It's a gaussian distribution of people with different coding and problem solving capabilities, but little engineering ones.

There are a couple of things that I believe are simple, effective yet difficult to do as engineers.

1. Don't open one's mouth when one is not sure about the topic;

2. Don't say anything without some good proof;

3. Be precise and keep it short.

Personally, I haven't managed to achieve any of them.

The art of doing science and engineering by Richard Hamming.

https://en.wikipedia.org/wiki/The_Art_of_Doing_Science_and_E...

Related articles on this guy website ring true with me, even though he doesn't give a "solution" to improve

https://www.seangoedecke.com/weak-engineers/

This other one had a "criticism" that hit me hard

https://www.seangoedecke.com/being-right-a-lot/

I don't do many assertions on our systems, out of fear of getting things wrong. This shows the holes in my understanding.

Feynman’s Six Easy Pieces: https://www.goodreads.com/book/show/5553.Six_Easy_Pieces

Engineering, regardless of practice, is two things: process and measurement.

If you want to think like an engineer there are only facts and assumptions. Your assumptions will generally be wrong, often by multiple orders of magnitude. Just accept that.

In everything you do follow established processes step by step and measure absolutely everything with numbers. If you are capable of doing that you are thinking like an engineer.

Engineers, outside of software, are also subject to audits and liabilities. Evidence is your friend.

Not so much thinking - but actions. Roll up your sleeves and take ownership of issues and understand it as best you can before asking for help. If you ask for help then you should be able to say "I think this does ..." rather than "I dont know how this works"

You can only learn some complex skill by doing it.

Understand what engineering job is and go build up the skill from smallest achievable goal.

There is motivation special”thinking”, don’t cargocult it )

Studying engineering in an academic setting is an ordinary way to develop an engineering discipline.

Reading about engineering is not practicing engineering…sure it might be part of an engineer’s practice once they are practicing. But it is not solving real or pretend engineering problems.

Sure there is also learning engineering on the job from experienced engineers. But again, that’s not a book.

To frame it another way, engineering practice is about doing things correctly to solve the problem. Not in the way that benefits yourself. That’s why people can trust engineers.

Reading a book is not the way the problem of becoming an engineer is solved. Good luck.