📎 Webclip
Ten Principles for Growth as an Engineer
Thread by Thiago Ghisi summarizing Dan Heller’s ten principles for growing as an engineer. The focus is on thinking beyond coding to business impact, initiative, communication, project ownership, and long-term mastery of tools and education, framed as lessons the author wishes he had learned earlier.
Reading notes#
- Dan Heller frames these principles as lessons for engineers that he wishes he had learned many years earlier, ideally at the start of his career.
- Engineers are encouraged to think in terms of business value, reasoning like a CEO about how their work helps the company succeed and making informed tradeoffs on quality, features, and speed.
- The job is presented as broader than writing code, emphasizing responsibility for making good decisions that further the company’s goals.
- Engineers should refuse to remain blocked, using persuasion, escalation, or technical creativity to keep work moving and ensure their efforts create value.
- Taking initiative is highlighted as critical, countering the belief that others are fully in control; engineers should own their team and company mission and act when they see needed work.
- Managers are described as depending on engineers’ creativity and intelligence rather than solving everything themselves.
- Strong, concise technical writing is described as a key skill for collaboration, persuasion, teaching, and informing different audiences.
- Written communication should account for the reader’s knowledge, aim for clarity and brevity, and typically include a short summary (tl;dr) near the top.
- Engineers are urged to own their project management by understanding dependencies, assigning ownership, and summarizing plans and status clearly.
- Proactive stakeholder communication on plans and progress, along with practicing how to run meetings, is tied to the ability to handle larger projects and prepare for leadership roles.
- Growth is framed as the engineer’s responsibility: pursuing mastery and making learning a daily habit, even in very small time slots.
- The thread mentions subscribing to mailing lists and seeking out papers and books as part of owning one’s education, though that specific list is cut off.
- Mastery of core tools such as editors, debuggers, compilers, IDEs, databases, network utilities, and Unix commands is portrayed as a major amplifier of development speed.
- When encountering new technologies or commands, engineers are urged to explore them more deeply than seems immediately necessary.
- Proactive, structured communication is linked to building confidence and goodwill with collaborators and fostering a culture of learning and camaraderie.
- Sharing knowledge and keeping stakeholders regularly updated on goals and progress are presented as ongoing responsibilities.
- Collaborating with others is described as a way to increase leverage and visibility, extending impact beyond one’s own code.
- The text connects advancing as an engineer and in one’s career with having influence that goes beyond individual technical contributions.
- Professionalism and reliability are defined in terms of punctuality, preparation, attention in meetings, and following through on commitments.
- Engineers are advised to communicate early when problems arise, maintain composure, and voice objections in a professional manner.
- The principles are sourced from “Building a Career in Software: A Comprehensive Guide to Success in the Software Industry.”
