The Guiding Principles of a Great Software Engineer

🧑‍💻 Act like an owner.

• This means: Taking full responsibility for a project as if it were your own business. It involves:
  • Thinking end-to-end, beyond just writing code, from conception through support.
    • Proactively identifying and solving problems, even if they fall outside your immediate designated tasks (e.g., creating missing infrastructure if needed).
    • Actively seeking clarity rather than waiting for it.
    • Defining what success looks like and how it will be measured.
    • Committing to supporting the project post-launch.
    • Being driven by a desire for personal growth and to achieve higher leverage in your contributions.

🧩 Relentlessly work to reduce complexity.

• This means: Striving to make systems as simple as possible to enhance understandability, maintainability, and the ability for others (humans and AI) to contribute effectively. It involves:
  • Focusing on making code easy to understand, debug, and deploy.
    • Using foundational “building blocks” (like well-defined APIs, message queues, data access layers) to compose services that are scalable and reliable.
    • Prioritizing the achievement of outcomes through software, rather than focusing on specific technologies for their own sake.
    • Understanding that simplicity is key to building software that can scale with user growth and engineering team growth.
    • Being opinionated about tools and building blocks with the aim of empowering other engineers to contribute meaningfully and quickly, thereby fostering progress and motivation.

🗣️ Act swiftly to learn, creating tight feedback-loops with users.

• This means: Prioritizing rapid, iterative development cycles to gather insights directly from users, rather than getting bogged down in extensive upfront planning or premature optimization. It involves:
  • Approaching new functionality by striking a balance between leveraging existing building blocks and maintaining simplicity, focusing on delivering core value first.
    • Implementing the most critical functionality initially, especially for beta tests or phased rollouts, and deferring non-essential elements (e.g., advanced caching) until user feedback and performance data indicate a clear need.
    • Skillfully identifying and making trade-offs, understanding that while some optimizations can be postponed, foundational aspects (like data models) often require careful consideration early on to prevent costly future revisions.
    • Being driven by the goal of tightening the feedback loop with customers to iteratively refine the product and ultimately create solutions that users find truly valuable and delightful.
    • Recognizing that quick, iterative progress based on real-world usage is more effective than prolonged speculation about user needs or system performance.

✨ Humbly embody engineering excellence and inspire it in others.

• This means: Serving as a role model for high-quality engineering by consistently applying sound principles in one’s own work and, through these actions and a genuine desire for collective improvement, motivating others to elevate their own practices. It involves:
  • Personally and visibly demonstrating the principles of great engineering (such as “Act like an owner,” “Relentlessly work to reduce complexity,” and “Act swiftly to learn, creating tight feedback-loops with users”).
    • Leading by example, for instance, by taking full responsibility for supporting developed features without complaint, and by focusing on fixing problems constructively when they arise, regardless of who wrote the code, rather than assigning blame.
    • Actively seeking feedback on one’s own work and practices, thereby modeling a commitment to continuous growth and humility.
    • Making one’s work and decision-making processes visible to others, but doing so in a humble manner that encourages learning and collaboration rather than self-promotion.
    • Being motivated by a genuine desire to see others grow, contribute at a higher level, and to scale effective engineering skills and mindsets throughout the team or organization.