📎 Webclip
11 Growth Principles to Become a Valued Software Engineer
The post says code reflects the principles of the engineers who write it, and that the most valued engineers are distinguished by growth principles that make them more productive and useful to the company. It lists habits and attitudes that support that goal, from technical skill with tools to a mindset that accepts change.
Reading notes#
- Good programming includes deeply understanding the tools you use, such as the IDE, debugger, Unix commands, CLI, and editor.
- Learn every day, because programming changes quickly and staying a student helps you keep up.
- Communicate clearly and often, especially when working remotely, because misunderstandings are common and frequent communication builds trust.
- Improve writing for email, Slack, and other messages by considering who the message is for and what they need to know.
- Unblock yourself by switching tasks, asking a colleague for help, or escalating the issue instead of letting productivity fall to zero.
- Own your projects by running meetings, knowing the people involved, writing summaries and plans, and keeping stakeholders informed.
- Treat your work like running a business and make decisions with the bigger picture in mind, not just your own team.
- Act professionally by being on time, prepared, respectful, attentive, and not letting emotions or complaints dominate your conduct.
- Prefer done over perfect, because waiting for perfection slows delivery and software is usually released in imperfect early versions.
- Expect change, since errors, customer requests, and company pivots will require code to be modified later.
- Learn when to say no, including to extra features or unnecessary code, when the software can reach its goal with fewer moving parts.
