> software engineering IS "factory" work because its the grunt work of building what should be a well understood system So what are you implying here? That we

> software engineering IS "factory" work because its the grunt work of building what should be a well understood system So what are you implying here? That we should go the Waterfall route and have 100% clear and finished specs? Good luck with that buddy. You're just shifting the real problem outside of your "software engineering" space. In my 20 year career, I've never built a "well understood system". Some things can be built 10 times faster with the right idea. Some features can be supported by a single, simple one. Some screw-ups can take forever to fix. 100% code coverage won't give you bug free software. Building software is all about the skills of people (developers, analysts, managers, testers, ...). The better the people, and the more power you give them, the better your project will go. If you hire bad people and have to put processes in place so they don't screw up, you're in trouble.