no, software should be designed to work for as long as necessary, because we're responsible professional and don't want to squander other people money on infini

no, software should be designed to work for as long as necessary, because we're responsible professional and don't want to squander other people money on infinite perfection the whole bit is nonsensical included the parallels with civil engineering, bridges are built with tolerances, maintenance schedule, and a disposal plan for when maintenance cost become higher than replacing the bridge, because nothing in this world actually lasts. heck our internet is built around operating systems that didn't exist 25 years ago. imagine investing capital and sink opportunity costs in delivering the perfect vax typing program... mind, this is not to say that all software should be quick and dirty. but the conscious engineer knows whether it's building infrastructure to last decades or a temporary bypass to support some time limited traffic spike. the important bit is to ask the stakeholder what's more appropriate. I also want to see people build their own json parsers at acceptable level of performance, possibly as streaming parsers instead of just gobbling everything in memory. imagine wasting a month on building that and then having to defend your choice every time a bug or a malformed input causes silent data corruption somewhere in the backend. http://seriot.ch/parsing_json.php http://seriot.ch/parsing_json.php