Lately I’m seeing people defend the lack of junior cloud engineer positions by saying “cloud isn’t an entry-level job.” If that’s true, it’s quite an indictment of our industry, isn’t it? You’re telling me that after years of refining and abstracting and tool-building, cloud systems still require builders to recapitulate their entire history of IT on their CVs? If we can’t make cloud engineering accessible to new builders, what are we even doing here?

5 things I've learned the hard way about multi-region / multi-cloud:

1. Building your own control plane, whether cross-region or cross-cloud, involves cost and complexity that you will have to deal with every day - not just when a managed service has downtime. 2. More often than not, cloud incidents will look like partial degradation of downstream services, delayed event delivery, or reduced access to management APIs rather than a binary “up/down” state.

OK. Here are ten things I freakin’ love about Google Cloud’s approach to identity / accounts. 1. You are YOU! Every user is just a Google account (personal or corporate) that works across projects. Lowers the barrier to entry, makes cloud feel like an extension of things you already know.

Happy Monday! I seem to have a bunch of new followers, so here is a thread of 10 of the most popular things I've written about cloud and tech over the last couple of years. 10. "The career-changing art of reading the docs"

Follow this one weird trick for a couple of years and you'll be able to perform magic - that's a promise

acloudguru.com/blog/engineeri…

I think AWS Proton just clicked for me.

It’s Conway’s Law-as-a-Service. AWS is reasoning backward from the [ central cloud team / app dev team ] org pattern present in many enterprises, and providing a tool that explicitly bakes that structure into how CI/CD pipelines and environments are baked and shared.

As part of my job, I edit a lot of writing by other devs. Rarely, if ever, is their work "too concise".

My #1 tip for engineers who want to become better writers:

Write fewer words, more frequently.

Thread -> The most common mistake I see from new writers is long paragraphs with a high word-to-idea ratio.

"If I'd had more time, I'd have written a shorter letter" isn't just an old joke.

Contrary to what you may believe, you don't have "nothing to say". You probably have too much.

Introducing the #CloudResumeChallenge. I'm volunteering my network to help you get your first job in the cloud. But I can only share a certain kind of resume. Thread -> forrestbrazeal.com/2020/04/23/the… First, you must not have prior professional IT experience on your resume (except maybe something super entry-level like helpdesk), and you can't have a college degree in a tech-related major. I want to focus on helping new people break into the industry. #CloudResumeChallenge

Can serverless architectures be "code-wise, cloud-foolish?" Sure! Let's count the ways ... (1/) Writing a Lambda function when a direct service integration does the same thing #CodeWiseCloudFoolish

It's time to share my next thing. But first -- more Strange But True Cloud Facts! (thread/) The cloud won't save you money. This is bad news if the primary goal of your business is to spend less money. #StrangeButTrueCloudFacts

Lambda Provisioned Concurrency is here! I had a chance to experiment with the feature before release, and while there's no beating @theburningmonk's thorough review, I do have a few thoughts and caveats. 1/

lumigo.io/blog/the-end-o… @theburningmonk First, know that this does not change the fundamental behavior of Lambda. You are NOT getting long-lived, stateful, provisioned instances. AWS will still recycle the underlying execution environments every few hours. (Don't complain, you want this.) 2/

#StrangeButTrueCloudFacts ... a thread (with an exciting announcement at the end) 1. There are still more production apps running on mainframes than in the cloud. Like, *way* more. #StrangeButTrueCloudFacts