That&#x27;s because, for an extremely large portion of the &quot;businesses who employ programmers&quot; market, most of that image is just not a thing they do. I&#x27;ve never seen an ASP.NET consultoware shop do anything with PaaS, containers, load balancing, package managers, automated server management, search, automated configuration management, security auditing, or real UX design.<p>You usually have one guy or a very small team managing an on-site closet full of hardware, which is running an operating system you&#x27;re probably not going to like, that is <i>maybe</i> virtualized, if you&#x27;re lucky. That&#x27;s all lumped under IT, so the same people are responsible for answering support calls, setting up email accounts, and installing network connections.<p>Then, on the development side, you have a particular web server, database, programming language, and application framework being used for <i>every</i> project, no possibility of doing anything else. The people who are hired here are expected to be able to make fool-proof instructions for the IT staff to be able to install the programs on the server.<p>And there is nothing in between. IT owns the hardware were the software runs, but they know nothing about how the software is made or what it needs. If something goes wrong, there had better be a developer on hand to &quot;just fix it&quot;. Developers own the software, but they have zero access to the hardware, so preparing deployments is basically a ritual of finding the IT guy who hates the lead developer the least and hope he has time play telephone game on script runs that the developer massages based on his screenshots that he pastes into MS Word documents and emails.<p>If you&#x27;re particularly lucky, your team figured out what sort of joke your &quot;Corporate IT infrastructure&quot; actually is and they communicate completely outside of the issue ticket tracking system that you installed to try to measure productivity because you have no clue how to evaluate anyone&#x27;s work because you only have an MBA and have no idea how software is actually built or what kinds of problems IT departments actually face.