Devs often have a hot and cold relationship with their sys admins. On the one hand sys admins love nothing more than to prevent us from doing our job (“need admin rights on your local pc? – sorry its against policy”, “need access to the command line? – sorry its against policy”…).
On the other hand we are having to be nicer and nicer to them as they hold the keys to the .net security policy can of worms. And more and more we need to know more and more about systems policies, office admin policies, and group policies.
Absolutely THE biggest thing (by a mile) I love about Excel/VBA projects is the utterly trivial deployment. Its so completely trivial most of us don’t even consider it as a separate phase in the development cycle. Its passed UAT (User Acceptance Testing) , its live. Thats it, no separate package and deployment phase, no dependencies worries (unless you used non Office components). This means as a business developer I concentrate solely on solving the business issues, I don’t get bogged down in system stuff, and admin fluff.
I accept there is a management and security trade off to this ease of deployment, but personally I’m happy to take that trade. One other big benefit is I rarely have to deal with those sys admin jobsworths. (If you are a nice sys admin, or you know one – sorry for the stereotype).
I wonder if the .net way is a step too far in the direction of Administrivia, and away from solving business problems. (Or maybe I shouldn’t be so dismissive of the security aspect?)
What do you think?