sean goedecke

Generic software design advice is largely useless for real-world engineering work on large existing codebases. Effective design requires intimate knowledge of concrete implementation details, not abstract principles. The most valuable design discussions happen between engineers actively working on the system, focusing on specific subsystems, dependencies, and constraints. Generic advice has limited utility: guiding new projects, tie-breaking decisions, and ensuring cross-codebase consistency. Formal architect roles that design without implementation responsibility often fail because they lack the concrete understanding needed to create actionable plans. Engineers who design systems should be accountable for their success or failure.

You can't design software you don't work on

<p>Did you heard about windows maybe?</p>


<p>Non-tech examples like mc donalds’ ceo not eating mc donalds or big medical insurance companies’ ceos not needing affordable insurance just proves that we can all come up with unefficent (but profitable!) solutions for problems we don’t have</p>
