defines the problem specifically for themselves and others
breaks down projects and tasks with well-known finish lines and DoD
prepares a plan B upfront
knows real production data and its ranges + how will a solution be used out in the field (by another person or another machine)
measures performance and resources + reports and monitors
detects technical risks upfront and mitigates them
effectively and professionally communicates with all stakeholders
manages technical conflicts directly and professionally
learns and shares knowledge by circles (myself-team-company-community)
improves the system while planning frameworks of solutions
translated from my Hebrew post: https://nurnachman.wordpress.com/2025/09/22/%d7%9e%d7%a4%d7%aa%d7%97-%d7%aa%d7%95%d7%9b%d7%a0%d7%94-%d7%9e%d7%a7%d7%a6%d7%95%d7%a2%d7%9f/
adapted from https://adamj.eu/tech/2022/06/17/mike-actons-expectations-of-professional-software-engineers/