This a concise yet necessary shared observation on software design. The problem invariably becomes feature creep or inheriting someone elses working code. Not

This a concise yet necessary shared observation on software design. The problem invariably becomes feature creep or inheriting someone elses working code. Not every problem can be optimally fast, and also optimally sized for simplicity. As an alg coder of quite a few years of course I prefer and love simple easy to read, remember, and modify code. But then someone comes along and says, we need this fairly quick code, parallelized, ported to these other platforms, and faster than real time. Dynamically size and share memory as needed to scale to any number of available nodes, and have it driven by a GUI, but make those buttons overlay an elliptical earth model….. As you can imagine, writing simple (and reusable) code is a desirable thing for programmers. Unfortunately we don’t dictate the terms and requirements, real physical systems do. Sometimes deadlines trump both of the above, and getting something to work, means messy throw away code. I guess we could all agree never to write software like that, good luck getting consensus (herding cats made easy).