There are several great frameworks that help set standards for good engineering work. My go-to references are the principles of Lean Manufacturing, Manifesto for Agile Software Development, Bauhaus Principles, and Amazon Leadership Principles. And of course, The Frugal Architect.
Here’s how I think about good engineering work:
-
Less Waste, More Quality
Mix Lean’s waste reduction with Bauhaus quality standards and AWS’s excellence. Build solutions that work well and last. I’ve found that focusing on quality from the start actually saves time and resources in the long run - fewer bugs to fix, less maintenance needed, and happier users overall. -
Customer Empathy, Global Responsibility
Combine AWS’s customer focus with sustainable thinking. Make users happy while keeping an eye on environmental impact. It’s not just about building what users want - it’s about understanding their needs deeply and delivering solutions that work for them without excessive resource usage. Sometimes the simplest solution is also the most sustainable one. -
Form Follows Function, Function Shapes Future
Take Bauhaus’s famous rule and think ahead. Build flexible solutions that can grow and change over time. I’ve learned that the best designs naturally emerge from solving real problems, but we need to build in enough flexibility so our solutions can adapt as needs change. It’s about finding that sweet spot between solving today’s problems and being ready for tomorrow’s challenges. -
Iterate with Purpose
Use Agile’s step-by-step approach, but always know why you’re making changes. Each update should make things better for users. Small, frequent improvements are great, but they need direction - I try to make sure every change moves us closer to our goals and isn’t just change for change’s sake. User feedback is crucial here. -
Simplify to Amplify
Keep things simple like Bauhaus taught us. Simple solutions are easier to use and work better for everyone. I’ve seen complex solutions fail where simpler ones succeed. It takes more effort to make things simple, but it’s worth it when users can understand and use your solution without confusion or frustration. -
Pull Value, Push Sustainability
Use Lean’s pull system while thinking about the bigger picture. Let user needs guide you, but keep sustainability in mind. I’ve found this balance crucial - respond to real demand rather than pushing solutions nobody wants, but do it in a way that considers long-term environmental and social impacts. Sometimes this means saying no to features that would be wasteful. -
Bias for Responsible Action
Like AWS says, take action - but think about the impact. Move quickly, but make sure you’re doing the right thing. In my experience, it’s better to make a thoughtful decision now than a hasty one we’ll regret later. Being responsive doesn’t mean being reckless - we can move fast while still considering consequences. -
Craft for Legacy
Mix Bauhaus quality with modern innovation. Build things you’ll be proud of tomorrow. This isn’t just about code quality - it’s about creating solutions that stand the test of time and can be built upon by others. I try to write code and design systems as if I’ll need to explain them to someone years from now.
These principles help me stay focused when things get complex and remind me to build quality solutions while thinking about the future. It’s really just about having the right mindset - thinking about both the immediate task and its longer-term effects.