> Almost nobody is writing real novel software, they're just gluing together premade parts and managing the plumbing. You say that like it's a bad thing. One

> Almost nobody is writing real novel software, they're just gluing together premade parts and managing the plumbing. You say that like it's a bad thing. One man's "novel implementation" is another man's "unreadable and unmaintainable pile of hacks". I'm not saying we should all standardize on a single set of tools, but after the fourth project you've cleaned up that spends tens of GB of RAM editing XML files, you'd probably wish "uses a database" was a business requirement for every future project too (just as an example).