Chapter 13. Developers—Go Faster, Go Together
Editor’s note: In the introduction, we promised that we would refrain from preaching the value of cloud. Well, what’s a rule without a willingness to break it once in a while? This final essay takes a different approach: it looks different and has a different structure. This essay is for developers everywhere, reminding us that once in a while, a technical change may, in and of itself, be an extremely powerful motivator for unleashing the latent talent in your organization. With love, Google.
Disruption Arrives: Let’s Move to Cloud!
Recommendation: don’t underestimate how much a change in resource provisioning can impact your day-to-day.
It’s a cliche in the tech industry: your project is humming along, everything seems to be normal—and then the Monday morning meeting happens. Management has discovered a new truth, the perfect new tech strategy. Today’s shift: we’re moving to cloud! You sigh and mentally throw out the plans you had for the next few quarters. Disruption has arrived.
Good engineering leaders know that there is some truth to this—disruptive new mandates have a cost. The tech industry is certainly prone to fads and buzzwords, so you have to think very carefully when a new fad arrives on the scene: is this really going to improve outcomes for you? In the case of shifting to cloud, we believe there is a lot of benefit—for your project, your team, and even your happiness as a developer. ...
Get A Practical Guide to Cloud Migration now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
