1,032 karma · joined March 21, 2013
http://content.photojojo.com/photo-technique/tips/legal-righ...
Reading between the lines a bit I suspect this passerby was relaying instructions he got in some kind of "security" training ostensibly about terrorism. If he discourages you from taking the photo, and a real security incident can be avoided, so much the better. If he overplays his hand and, for example, tries to restrain you at the scene, this causes a bigger story and a blemish to his employer at the very least.
I think you handled it correctly. Bend, but don't break. Know your rights. Understand what is at stake and then decide if you want to risk standing your ground.
Right.
Even if your project only expects to use AWS can you say that for certain of all your projects?
If I take your approach and assert myself as the "gatekeeper" between some 300 software developers and the public cloud, I may enjoy some sense of control. This sense is false and doomed to be short lived. Sooner or later, these same developers will realize all I am is an interface and they will read documentation, find blogs, and internalize that they too can hit AWS APIs. Some folks call this "Shadow IT."
One thing we can agree on is fewer ops people overall. A huge chunk of the work I used to do in the ops role included buying gear, racking, stacking, building data centers, provisioning OS, networking, repairing, etc. In the cloud, all that is done for me. Staking out the middleman role doesn't hold any allure for me. I'd prefer to help lead the developers into a self-service model and show them how public cloud changes the rules of the game enabling them to change their perspectives, improve and rewrite their applications, and generally move much faster.
This model is working quite well for me today. I dare say the developers are equally happy. They certainly have questions about more traditional ops stuff. Those questions get answered and circulated around the team. Eventually, the questions start moving toward cloud ops stuff. How do we autoscale? What's the right AZ redundancy model? How do we setup Direct Connect? When should we use spot instances? That shows evolution and learning.
EC2 is not built for ops teams at all. It is built for developers. The VSphere/Xen analogy doesn't hold up. Amazon is explicitly abstracting away the physical and software stack that ops teams would build and mantain onsite. AWS gives you back an API and a reference client. Nothing to install, no physical hosts to buy, no network switches to configure. Simply focus on your compute requirements and go from there.
- How many hosts are there in a /23 network?
- Estimate ping time from your workstation to your local gateway? www.google.com? Server on the east coast from the west coast? Server in Europe from the west coast?
- What law(s) of physics control(s) the round trip times?
Same rules don't apply in dev and are counter productive there.
"and it seems they now have a full fledged solution for the problem, based on pretty much a reimplementation of AutoScaling, using machine learning and with a beautiful UI and they are really successful with it. Funnily enough, they even contacted me to sell that solution to my company and we are seriously evaluating it"
I went to watch stock ticker channels on PBS at homes and subscribe to Investor's Business Daily.
From there, I spoke with my parent's financial advisor and was able to make some small purchases to invest some of my family's real money.
He covers the nitty gritty details on mortgage collapse in an approachable and enlightening fashion. His book lends weight to your assertion about coastal discord.
Bought an iphone last year. Couldn't be happier.
https://developers.google.com/chart/interactive/docs/gallery...