"Now, the watchword to the development team is: it's not done until I can one-click deploy it."
I have apparently been spoiled somewhere along the line, because I really don't like having clumsy manual processes that involve software/computers. I was recently tasked with figuring out how some researcher's code worked (with an eye towards automating the use of their tools), and it took 8 pages to get most of the steps documented well enough that I could follow them. Steps like, "edit the path in line 977 to point to your input files, recompile, run, click button A..." -- i.e., things that should never have been done manually to start with.
How on earth people whose primary job involves writing code to do things for them can fail to automate tedious (and frequently error-prone) parts of their job is beyond me.
That said, many companies are still going to need to hire somebody to write the one-click deployment. Somebody will have to know how to interact with the cloud services, and how to get around all the little minefields and gaps left in the cloud service offerings, and odds are you aren't going to want to pay that person as much as you pay your developers that do the "real work." That's probably where the sysadmins will go.
It's simple : The people you are complaining about set these things up once on their computer and then forget about it. They don't realise how many things they have set up once along the years.
It is not until you appear that it's time for the app to be deployed elsewhere.
I have apparently been spoiled somewhere along the line, because I really don't like having clumsy manual processes that involve software/computers. I was recently tasked with figuring out how some researcher's code worked (with an eye towards automating the use of their tools), and it took 8 pages to get most of the steps documented well enough that I could follow them. Steps like, "edit the path in line 977 to point to your input files, recompile, run, click button A..." -- i.e., things that should never have been done manually to start with.
How on earth people whose primary job involves writing code to do things for them can fail to automate tedious (and frequently error-prone) parts of their job is beyond me.
That said, many companies are still going to need to hire somebody to write the one-click deployment. Somebody will have to know how to interact with the cloud services, and how to get around all the little minefields and gaps left in the cloud service offerings, and odds are you aren't going to want to pay that person as much as you pay your developers that do the "real work." That's probably where the sysadmins will go.