3 ms·
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
by svantana 4y ago
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.
- JacKTrocinskI 4y agoK.I.S.S. - Keep It Simple Stupid
- layer8 4y agoMaybe that should be retronamed to Keep It Simple Smart. ;)
- tommiegannert 4y ago> as simple as possible "I want that ASAP" just got a much more complex meaning.
- derrida 4y agoNICE
- jovial_cavalier 4y agoI can also see this turning sour, though. A problem with the mindset being discussed is that it makes it hard for people to collaborate, since everything gets complex and muddled. If you just move that problem from the shipped code to the tooling around the code, you haven't really gotten rid of it. There is still a big barrier to entry to contributing to the project, since people don't understand your infrastructure.
- mrits 4y ago"If you were that smart you wouldn't be working here with me" A line I used a few dozen times in my career