> The best engineers I know all strike a balance; keeping things simpler than a lot less experienced engineers would expect, and shipping something sooner. Yes

> The best engineers I know all strike a balance; keeping things simpler than a lot less experienced engineers would expect, and shipping something sooner. Yes. Because experienced engineers know that there is an exponentially-growing cost associated with complexity. So what may look like "clean quality code" at first look may in fact require an entanglement with frameworks that may or may not age well. And when the business needs start diverging with the vision of framework makers, then there's a world of painful molasses as the team struggles to either hack the requirements into the current codebase, or perform a costly rewrite.