I am one of those people - an academic type that likes to over-engineer, and at least partially …
I am one of those people - an academic type that likes to over-engineer, and at least partially work on embedded systems. What I've learned after two decades of experience is that it's best to apply most of that sophistication to tooling and supporting software - test suites, fuzzing, benchmarking, quality evalution, code and data generation, prototyping environments, automated reports, etc etc. All while keeping the actual shipped software as simple as possible.
Original discussionAsk HN: Strategies for working with engineers that are too smart?474 source comments · at import