On the contractor side, clients for some reason think the spec should be free and want to pay only for delivered code.
And I want a pony.
So why can't they move their feet out of the fire by verifying the public key themselves and uploading it into their own Gmail account?
No registrar can beat the verification of me pasting the public key from my own server and verifying the fingerprint out-of-band.
I can see how you might want GPO support if you're into it but for us it was great that we could deploy variants of one single file and support all 4 major OS platforms in use within our organization. We were able to provide preview releases of new Firefox builds that hadn't yet been tested with all the corporate apps and users could switch between them. As far as locking the settings or preventing auto-update, both of those tasks were both trivial and obvious.
Honestly Firefox and the rest of the products were fine to configure. The hassles really came a bit from what you'll have trying to automate any large organization, and most especially the politics from middle managers arguing about whether we could just push the update yet. Oh, the politics.
This is the fault of game " 'UI' 'designers' " who insist on drawing their own things instead of using system widgets. At best they act like the designer's preferred platform no matter where the application is running. More likely, they only approximate the coarsest features of the thing being emulated and leave the user with a constant feeling of frustration.
Really? You have to develop your own scrollbar?
(Scrollbars are actually a good example. I should note that this idiocy is now making its way into Web "design", where thanks to the "everything should be a tablet" crowd, you start to see people making custom scrollbars that hide unless you happen to mouse over the right place, and are too thin to grab with the mouse.)
As of late I've been noticing and commenting to friends about a growing disregard for spelling, grammar, and proper English as a whole. In school I was taught to never use contractions when writing a "professional" piece; I see that constantly now.
The problem is that your classes conflated a particular style (not using contractions) with basic rules of quality writing (spelling, grammar, and proper English). As a result, when you complain about the latter, people assume you are talking about the former and write you off as a dinosaur.
This is an unfortunate consequence of the arrogance of the last generation of English teachers. If, however, you're in fact using the latter to complain about the former, you're part of the problem and not the solution.
spell out any number ten or lower
This rule is harmful and it enrages me.
It seems to me that "Tweetspeak" and shorthand common to texting and Facebook messaging are now considered acceptable to journalism editors, particularly online.
It seems to be a common problem that people associate rules with media rather than giving any thought to what is necessary or unnecessary (e.g., "I'm not printing this onto a piece of paper, therefore I should misspell things"). Not to mention that while I think of it as a sign of respect for coworkers to write things in a legible manner for them, there sadly seem to be some who think the opposite.
rsync is brilliant at coping with interruptions
Just make sure you run it with -P if bandwidth is scarce and spotty.
I have had great experiences using the "Java EE" toolkit (basically just a combination of servlet and JPA technologies) and Spring MVC (Spring's front-end Web framework) to build nice clean modern Web sites and applications.
The great thing about this combination is nothing is too different from the stuff you've done before if you've done any medium- to large-scale Java programming before. Multiple vendors, commercial and FOSS, implement the specifications. JPA is one of the better ORMs I've seen (second only to CLSQL and probably more comprehensive, anyway). Most everything is done with simple annotations. And Spring is very well-mannered; you can take as much or as little as you like. Once I had to hook a Web front-end up to an application with a custom authentication system... it was cake to implement the Spring interfaces and suddenly my application was a fully acceptable auth provider for its own Web interface.
I have started a write-up on this at http://quadium.net/~vsync/tech/java-servers/ and my goal was to consolidate and smooth some of the information I had to scrounge over the years about the process. There is a lot of Java information out there but lots is outdated and much seems to assume familiarity or use of this or that IDE, and at least online I haven't found many comprehensive sources. That said, sadly once you get past the first bits of my write-up it gets to be more and more of an outline. But your perspective as someone familiar with Java but wanting to get into this aspect of it would be greatly appreciated.
If you're interested I believe a while ago someone on Reddit gave me some links to some Spring MVC tutorials that seemed decent as well. I can try to dig them up if you'd like.