um304

I hear people talking that it takes more than great programming skills for an engineer to be successful (particularly at fast moving tech companies). As an engineer, I have learned certain mindsets that have helped me do better in my work. For example: 1) an average to a problem well understood can potentially deliver bigger impact than a great solution to a problem poorly understood, 2) not all problems are worth solving and ability to prioritize them in terms of impact is a core skill, etc.

What mental models have you found useful in your career as an engineer? Or if you're not an engineer, what mental models you think engineers need to have to deliver bigger impact?

When working on hard problems, which might encompass unknown number of sub-problems, I often find myself procrastinating. Harder the problem, severer the procrastination. A psychology professor says that a person typically fails to begin a project when there is "confusion about what the first steps of the task are" [1].

When working on hard problem, you're bound to hit tasks of which you won't know first steps. You're likely to often find yourself in deep marshes with no way out. How do you stay motivated in situations like these? How do you not give in to procrastination?

[1](https://medium.com/@dr_eprice/laziness-does-not-exist-3af27e312d01)

Hi,

Job hunting is isn't easy for most of us. There are several tools available which can be used for the purpose, but some might be more effective than others. It's worth finding out what has worked for others before investing your time in any of them. So here's my question to the community:

How did you find your current job?

- Personal reference

- HackerNews (Who is hiring thread)

- Stackoverflow

- LinkedIn

- Other (please mention)