That's fine if you: • Never upgrade your tech stack. • Always use people of exactly the same level of skill. • Assume the project stops at implementing a sta

That's fine if you: • Never upgrade your tech stack. • Always use people of exactly the same level of skill. • Assume the project stops at implementing a static set of requirements given up front. • Assume the requirements are correct. • Assume there's no political dimension to the actual deployment and usage of the app, i.e. the project is just software and not a business change project. In practice none of these things are ever true. The business doesn't want a CRUD app, it wants an automated process that it probably can't explain, will change half way through the implementation and some of the employees may resist deployment of the software. And people expect software development to get cheaper and faster over time, as with everything else in life, so you can't exactly ship a Visual Basic 6 app in 2018 because that's what you happen to know best so you can easily estimate work with it.