It seems the whole tech world is full of developers.
Everyone and their mother (and my mother even) have learned to code and many are trying to start or change their careers to match. There are code bootcamps in every major city and it’s easy than ever to get started. Operations, however, remains a dirty word invoking images of pale nerds replacing wires in datacenters or manually parsing through log files. Companies make millions with their products that allow developers to “not worry” about anything outside of their code. In reality, ops is a challenging, interesting and rewarding field.
Ops has its own set of unique challenges. Figuring out how to fit everything together in a scalable, available and secure way requires not only a deep pool of knowledge but also creativity to come up with novel solutions as well as work with others in various disciplines. A good ops person has to keep up to date with all sorts of new techniques and technologies and is typically the first person consulted when a company is considering new technology. Ops is also rewarding, both in terms of personal fulfillment but also financially as cloud architects are more and more in demand every year.
If you’re interested in learning more about ops (especially cloud ops) RunAsCloud is always looking for interns. Email firstname.lastname@example.org to learn more!
There’s been a ton of coverage of the recently discovered Capital One breach. I’m generally very skeptical when AWS security makes the news; so far, most “breaches” have been a result of the customer implementing AWS services in an insecure manner, usually by allowing unrestricted internet access and often overriding defaults to remove safeguards (I’m looking at you, NICE and Accenture and Dow Jones!). Occasionally, a discovered “AWS vulnerability” impacts a large number of applications in AWS – and it also impacts any similarly-configured applications that are *not* in AWS (see, for example, this PR piece…um,…Read More