Every engineer should do a stint in consulting

I will die on this hill.

Hacker News has many opinions about this post; read them

Every software engineer and IT person should do a stint in consulting.

I’m not talking about becoming one of those contractors who are billed out by their companies as “consultants” but are really just serial hired hands. I’m referring to a true consultant role, where you are paid to bring expertise, give advice, and drive technical change.

There are a few different ways to land in a role like this:

  • Go into business for yourself, as an independent consultant. But running your own business involves a whole bunch of other skills like sales and networking. This post is mainly focused on how consulting helps you become a better engineer, so I won’t spend much time on the independent option.

  • Work for a consulting firm in a senior-ish role. Depending on your specific flavor of experience, you may find a role like this easier to obtain in a giant corporation like Deloitte or Accenture, a boutique specialist shop like Trek10 (where I used to work) or somewhere in between. In any case, the “staff consultant” option gives you the engineering experience of consulting but removes the challenge of filling your own sales pipeline.

  • Work for a tech company in a customer-facing technical role: say, as a post-sales engineer or solutions architect. This option may have more behind-the-scenes continuity than the other two, but is fundamentally the same skillset.

Whichever you choose, I believe that every engineer should spend a portion of their career doing one of those 3 things. Working as a consultant unlocks career gains that are difficult, if not impossible, to achieve as an in-house engineer or engineering leader.

The Consultant Superpowers

A bird’s-eye view of the industry

Once you’ve worked with a few clients, you’ll realize that most of them aren’t as unique and special as they think they are. They’re facing the same organizational malaise and borrowing against the same technical debt as everybody else. You’ll quickly start to become a professional pattern-matcher, applying things that worked in company X to the problem you see in company Y. To the extent that “best practices” in tech are a real thing, this is where they come from.

I think I heard someone refer to this process of best-practices-emerging-through-consultancy as “thought laundering,” which sounds awful but can actually be sort of cool. Over time, you get the opportunity to build a playbook for success in your discipline that works in, like, 80% of cases. Most people probably won’t fully buy into your ideas, but you’ll know they work. You’ll know. Nobody can take that away from you.

Working on high-impact projects

You don’t bring in a consultant to help you maintain the status quo, but to help you drive change. As a consultant, you won’t be maintaining the old ActiveDirectory server. You’ll be figuring out how to migrate 2,000 people onto Google Workspace. (See how I throw in little things like that, now that I work for Google? I’m such a shill. You should unsubscribe.)

A good consulting gig is a constant stream of the most interesting projects on the market, a smorgasbord of tasty ways to improve your skills.

Actually getting stuff done

Sure, I know the stereotype that consultants are charlatans who leave things in a worse mess than they found them. On the other hand, doesn’t that describe plenty of the people who work internally at your company as well?

The difference is that consultants are brought in specifically because they have no allegiance to anyone other than the executive who hired them. They can skip the politics and just point out what needs to be done, even if it’s obvious. Especially if it’s obvious. It turns out that many of the changes companies need to make - whether technical or business-y - do not require obscure eureka moments or months of discovery. The smart people inside the company are probably aware of the elephants in the room already. They’re just too trapped in bureaucracy and broken processes to fight back.

This is how McKinsey can send 23-year-old analysts into the world’s biggest companies and still be taken seriously. They’re professional elephant-pointer-outers, not necessarily creative problem solvers. If you can work with a consultancy that engages at the executive level, you may find that you’re able to get more done in a few weeks than your in-house counterparts could ever do on their own.

Empathy for customer needs

You won’t be seven layers of teams away from the customer anymore, writing internal tooling and hoping everyone agrees you should still get paid. When you consult, there are zero filters between you and the effectiveness of your work. Consultants who don’t deliver as promised don’t last long. So you get good at listening, at documenting, at showing the value of your work. You learn to solve real problems, not fake ones - because that’s how you get paid now.

Improved "mean time to competence" on new skills

You’re not being paid consulting rates to learn on the job; your ramp-up time for any new technologies you encounter has to be extremely quick. Learning how to learn becomes a more important tool in your belt than any language or framework. Over time, this means you’ll surprise yourself by how quickly you assimilate new information.

I said a stint though, not necessarily a whole career

Consulting has downsides, and they multiply the longer you stay in the field. Even assuming the ideal situation, with an honest team and cool clients, you’ll start to deal with stuff like this:

Constant project churn is fatiguing

I mean, new projects are exciting, but at some point you just start to want to work on something familiar for a little bit. I genuinely don’t know how people deal with this after, like, 20 years. Context-switching just strips your gears after awhile.

No skin in the game

You’ll be graded on a short time horizon as a consultant. You’ll meet your deliverables, get paid, and move on to the next gig. This limits the scope of the change projects you can be meaningfully involved with. It also decouples you from the long-term business outcomes of your work. Unless you have unusually epic relationships with your clients, you may someday find yourself wanting to be more of a player, less of a coach.

Being a professional “expert” is hazardous to your growth

Cops, politicians, and consultants have this curse in common: they’re professionally incentivized to avoid admitting that they might be wrong.

When you walk onto a client site, you’re not there to learn, mess around, make mistakes, and try again. You’re there to know more than the client, get things right the first time, and make the VP look smart for hiring you.

I always found this to be a stressful and not particularly honest arrangement. I’m not an expert, I’m just a guy who reads the docs. I didn’t like having to project an air of competence that I didn’t always feel. Mainly because I was afraid I would eventually convince myself that I was an expert, too, and settle forever into the lowest point on the Dunning-Kruger curve.

Billable hours are the worst

Sorry, they just are. They suck. Paying for value aligns incentives better for everybody, and yet nobody wants to do it.

So why consult?

To wrap all of that up simply: while consulting is stressful and has weird incentives, it’s also a shortcut to getting very senior, very fast. It’s like mainlining 10 years of experience in a quarter of the time. You’ll start to think about tech in a business context. You’ll build your network. And when you do go back in-house, you’ll be the well-traveled engineer whom everybody will look to for insight.

I recommend to anyone who asks that they do at least a couple years of consulting at some point in their career. Be careful if you choose to work with a firm, though; plenty of them have richly-deserved reputations as “body shops” that burn up people in the service of horrible clients. I list some trusted consulting shops in my Best Jobs in Cloud updates, and suggest starting there.

Links and events

As mentioned above, I work at Google Cloud now! I tried to explain why on this podcast with Corey Quinn, but I think I should probably do a blog about it at some point as well. Staying uncomfortable is a key growth signal for me, and I definitely feel the scariness of leaving the warm and friendly AWS Hero community for the other cloud. More to come here.

Also, the Cloud Resume Challenge is now a book and a hand-curated jobs newsletter. You can give both as a gift to the aspiring cloud engineer in your life - just click the little “gift” icon at checkout. We all got to this point in our careers because somebody took a chance on us; let’s pay that chance forward.

Just for fun

You have superpowers!

The best jobs in cloud: Aug 26, 2021

AWS, Verizon, Rocket Homes, and more.

This is a free preview of my hand-curated “Best Jobs in Cloud” newsletter. To get the best cloud jobs in your inbox biweekly, upgrade to a paid newsletter subscription or just buy the Cloud Resume Challenge book!

This week’s sponsors: Trek10, Stedi

General reminder to be respectful of our referrals’ time and take their restrictions at their word; don’t contact a Canada-only posting if you are based in the US, don’t apply to a senior position if you have no experience, etc.


Junior jobs

(little to no prior cloud experience required; we’ll train you)

Associate 5G Cloud Solutions Architect at Verizon

Location: Remote, but you have to live somewhere in the US

My contact at Verizon says: Verizon has begun its foray into cloud computing and you get to be at the forefront of our Solution Architecture, Cloud Engineering, and Developer Advocacy efforts. 5G edge computing is an entirely greenfield way to design, implement, and deploy applications and through this team, you will become an expert in the cloud architecture pattern of the future.

Inside track to apply: Email Robert Belson and mention this newsletter

Got junior job openings? I’d love to feature them in a future issue! Just fill out the quick form here.


Mid-level jobs

(a couple years of cloud/DevOps-type experience required)

Launch sponsor: Stedi

Stedi

  • has a huge vision for transforming B2B transactions and communication

  • is led by a great CEO

  • is fully serverless

  • is fully remote; you can live anywhere in the world

  • has a very high talent bar

  • Is looking for both mid- and senior-level folks (no juniors at present, please)

  • has $70m in funding from top investors

  • pays top-of-market salary benchmarked to the Bay Area (regardless of where you are located): $170k-$250k level-dependent base + equity + benefits

A word from Forrest: Some of the people I know and respect best in this industry work at Stedi, including multiple former coworkers of mine. If you want to build pure serverless systems with incredibly intelligent people that really care about getting things right, Stedi is the place to be.

Inside track to apply: careers@stedi.com; mention this newsletter.

Azure Cloud Architect Consultant at Tidal Migrations

Location: Remote, but legal Canada residency is required.

My contact at Tidal says: Did you ever yearn to work for a startup but never had the opportunity, missed your chance, or were too risk-averse? With Tidal Migrations' portfolio of long term blue chip customers, you have a second chance without the risk. Putting your cloud skills to work now with Tidal Migrations will give you that chance to get in early and enjoy the special camaraderie unique to young companies that have found the sweet spot in their market.

Inside track to apply: Send your resume to this handy address!

Software Development Engineer - AWS Identity & Access

Location: In office (Arlington, Berlin, Cupertino, Herndon, Seattle, Toronto, Vancouver)

My contact on the AWS Identity team says: As a member of the AWS Identity team, you will work on services that every AWS customer uses and on distributed systems that scale as AWS grows. This means you will help build end-to-end solutions across AWS, and innovate by using cutting-edge technologies and techniques, such as automated reasoning. As an Access Analyzer engineer, you will build services to simplify permissions for all AWS customers. You will innovate by using data analysis techniques, develop systems with a high bar for security and accuracy, and deliver new and improved features that make it easier for customers to manage access to their cloud assets.

Inside track to apply: Send your resume to Rachel Blackburn; mention this newsletter

Full Stack Engineer at CloudTamer

Location: Anywhere: true global remote!

My contact at CloudTamer says: Our Full Stack Engineer will be adept at working on every facet of the cloudtamer.io application – from the data storage layer to the user interface. You’ll develop on loosely defined requirements, provide technical guidance to peers, and advance the product from a technology perspective.

Forrest says: The CloudTamer team is up-and-coming, and working on a rich set of problems. I’ve also enjoyed every interaction I’ve had with their team, which isn’t a given. They seem like good folks.

Inside track to apply: Send your resume here; mention this newsletter

SRE/Cloud/DevOps Engineer at Cheetah Digital

Location: Remote anywhere within the US, UK, India, Manilla, Costa Rica, Kuala Lumpur

My contact at Cheetah says: Our journey to the cloud is helping our customers deliver better results to our clients, partners and ultimately end users. Our cloud team is focused on cloud native applications and migrations to AWS.

Forrest says: I have tremendous respect for Justin Brodley, who leads cloud at Cheetah, dating back to his time leading cloud transformations at Fannie Mae - he “gets it” and is great to work with. You’ll be in a good spot here.

Inside track to apply: DM Justin Brodley on Twitter or LinkedIn


Senior-level jobs

(Significant cloud experience; you can lead a team or teach others)

Principal DevOps Engineer at Roche

Location and salary: Fully remote within the US, up to $200K depending on experience

My contact says: Roche has been around for 120 years. This is not an 80hr/week startup, rather it's a solid enterprise with the resources to invest as needed, and right now, that's top-tier people. We are an AWS shop currently using Terraform, Cloudflare & Splunk. Roche is committed to a superior level of software craftsmanship. People with the drive, motivation and vision will excel here.

Inside track to apply: Apply to job posting directly and email Bruce Edge with contact info & resume.

Launch sponsor: Trek10

An AWS Premier Consulting Partner focused 100% on modern application development and serverless, Trek10 is growing fast and hiring quite a few folks to work on large, interesting projects, including Cloud Engineers, Cloud Architects, and AWS Cloud Architects - Kubernetes. Both mid-level and senior-level folks are encouraged to apply.

A word from Forrest: Longtime readers may remember that I used to work at Trek10. The team is humane, humble, good at what they do, and fully distributed. A fantastic place to level up your career. Can’t recommend them highly enough.

Location: Somewhat global remote, but due to timezone constraints they would prefer NAMER or EU-based folks at this time.

Inside track to apply: Send your resume to Megan Bivin with headline “Forrest's newsletter”. They’ll be expecting you.

Senior Kafka Engineer or Team Leader, Engineering at Rocket Homes

Location: Fully remote within the US or Canada

About the Kafka role, my contact at Rocket says: Work with great technology like Kafka, Node.JS, AWS and TypeScript along with helping to grow a team of like-minded excited teammates. We offer the support and benefits of a big company while still having the vision of a start-up. The best part is you get to bring the best of you to a new team that needs your vision and excitement.

About the team lead role, my contact says: We're looking for an experienced AWS cloud leader to lead our Enterprise Infrastructure Engineers. They are an experienced, high-performing team building infrastructure for some awesome applications! You've got the opportunity to make a huge impact on a startup-sized culture with enterprise-type benefits and opportunities for growth.

Forrest says: The Rock family of companies is solving some super interesting web-scale problems - plus their Detroit offices are very cool!

Inside track to apply: Send your resume to Dean Simmer for a referral.

Cloud Engineer at Syapse

Location and salary: Fully remote within the US; competitive salary with pre-IPO stock options.

My contact at Syapse says: Our company is dealing with large data analytics platforms to speed precision medicine insights. The Cloud Engineering group is innovating with Argo CD and other tools to create a premier pipeline that accommodates complex configuration management and data migrations.

Inside track to apply: Shoot your resume to John Marx.

Technical Program Manager at AWS Organizations or Software Development Manager at AWS Identity

Location: In-office in Arlington, Berlin, Cupertino, Herndon, Seattle, Toronto, Vancouver

My contact at AWS says: As an AWS Organizations technical program manager, you will own and drive projects to ensure a consistent, multi-account management experience for all AWS customers. You will collaborate with internal and external customers to articulate requirements, streamline processes, and simplify multi-account management.

As a resource management software development manager, you will lead engineering teams that build services customers use to organize, explore, and act on their AWS resources at scale. You also will collaborate with leaders across AWS to deliver resource-management features that are essential to customers every day.

Inside track to apply: Send your resume to Rachel Blackburn; mention this newsletter

Senior Networking Engineer at Cheetah Digital

Location: No restrictions; true global remote!

My contact says: Our Senior Networking Engineering role is a key part of our network team defining our hybrid networking stack, future programs and architecture. For a candidate who is looking to transition to network architect soon this is a great opportunity with a clear path to Network Architect in 18-24 months.

Forrest says: Same sentiment as on Cheetah’s mid-level posting. Justin Brodley is an AWS legend and also on my bucket list of “great people I’d like to work with directly someday.” You’ll be in a good spot here.

Inside track to apply: Hit up Justin Brodley on LinkedIn or Twitter DM

Manager of Infrastructure Engineering at HNI Corporation

Location: No restrictions; true global remote!

My contact says: In this position, you will provide global technical guidance and leadership in projects involving a variety of infrastructure technologies (cloud, storage, compute, network, etc). You will organize resources around the execution of business objectives in a highly dynamic environment and will provide technical leadership and direction on the latest technologies and technological opportunities needed in order to give the business a competitive advantage. It’s highly visible and will provide the opportunity to be a part of HNI’s continued digital transformation journey.

Forrest says: This is a chance to get in on the ground floor of a massive cloud transformation at a Fortune 500 company. Not necessarily for the faint of heart, but I have great trust in the leadership.

Inside track to apply: Just ping Forrest on this one (reply to this email is fine)

Senior Backend Engineer at Vendia

Location: Global remote, but you need to be able to operate within +/- 5 hours of the US Pacific Time Zone.

My contact at Vendia says: At Vendia, we’re creating the world’s fastest and most scalable platform for developing and running universal applications. We combine the best of serverless, distributed ledgers and massively scaled cloud services to help customers solve their hardest data sharing and integration challenges. Be part of the movement and join a team of experts that built industry-changing services like AWS Lambda, DynamoDB, API Gateway, Step Functions, S3, and many more.

Forrest says: Tim Wagner, founder of Vendia, is the guy who invented AWS Lambda. You’ll be working on the cutting edge here.

Inside track to apply: Indicate on application that you found Vendia through this newsletter


Leadership

(Director-ish titles and above)

Head of Consulting Services at The Duckbill Group

Location and salary: Remote, but must be legally authorized to work in the US. $180K + bonus / profit share

My contact (OK fine, it’s Corey) says: This role will scale out the consulting function of a surprisingly-well-known consultancy. Our approach to consulting is radically different than most firms, our reputation is sterling, and our guiding philosophy is "this industry takes itself far too seriously; we aim to change that." Plus, our mascot is a platypus with an attitude problem.

Forrest says: I can’t even imagine what it would be like to work for Corey Quinn. And I have a pretty good imagination.

Inside track to apply: Email Corey

Director of Product Management at Vendia

Location: Global remote, but you need to be able to operate within +/- 5 hours of the US Pacific Time Zone.

From the listing: As Director of Product Management for Vendia Share, you will own and drive product strategy and roadmap for Vendia’s flagship product. 

Inside track to apply: Indicate on application that you found Vendia through this newsletter


And that’s it for now! Again, if you are hiring and want to see your role in the next issue, please pass it along via the intake form.

I would also love your feedback on this issue - just hit reply or comment, and let me know what you think. Too much AWS? Would you like to see more variety of roles in areas like PM and devrel? Is there a geographical area you want to see more jobs in? Please let me know - this newsletter will evolve and improve only if we communicate!


Coming soon: the best jobs in cloud

Let me give you the inside track on great cloud jobs.

It’s a big week here at Cloud Irregular.

Tomorrow this newsletter comes full circle with the launch of the Cloud Resume Challenge book, which began as a post right here in April 2020 and has since blossomed into a global initiative helping countless people on the road to their first job in cloud.

The e-book is 50% off for a few more hours until launch, and wraps up everything I’ve learned about the challenge in partnership with the worldwide challenger community:

  • 130+ pages of tools, tips, and challenge add-on ideas

  • The secret “17th step” that makes your project stand out above the crowd

  • How to write a challenge blog post that will get the right kind of attention

  • Four all-new bonus projects covering AWS, Azure, GCP, Kubernetes, Terraform, and more

  • Proven challenge-to-job strategies for both career-changers and upskillers

  • Case studies from challenge champions: how they got hired, what they learned

Plus, there’s one more perk for book buyers that I’m incredibly excited about. Tomorrow, I’ll be sending out the first issue of something I’m calling The Best Jobs in Cloud.

But first: how exactly do you find a good job?

A big part of the Cloud Resume Challenge for me has been connecting tons of champions to hiring mangers within my personal network. I love doing this (despite the number of LinkedIn DMs it requires), and I wanted to do it for as many folks brand-new to cloud as I could.

What I did not so much anticipate was that many established engineers would also reach out asking for help getting their next gig.

When you think about it, this makes sense. For the most part, working engineers are doing just that: working. They’re not spending long hours building their professional network, tweeting or blogging or whatever. And so when the time comes for a job change, they often feel like they’re starting from scratch.

Sure, there are tons of opportunities out there for people with experience. But that creates a problem of its own. How do you separate the signal from the noise, the great jobs from the terrible ones, ensuring that you won’t be burned out and back on the market in three months? (Just as the great engineers aren’t usually on the market, a lot of open roles out there are … open for a reason.)

Some of us in the industry have tried to solve this problem by encouraging all engineers to build thriving professional networks in their spare time. I have also encouraged this, and still do. But I’ve come to accept that it’s not reasonable to expect every programmer, sysadmin and engineering manager to become their own personal brand guru.

So what to do? You could check out job boards, but those are noisy and have weird incentives. You could hope that someone you know happens to have a great opportunity open exactly at the time you’re getting fed up with your current role. Hope isn’t much of a strategy, though.

I’ve come to realize that the best solution is the one I’ve been running ad-hoc off the side of my desk for the last 16 months: editorial curation. Outsourcing your networking to a friend who can swing you internal referrals to companies they trust. Basically, I’ve been acting as a talent agent for engineers, both junior and senior. And I figured it was time to put some process around this.

I’ve realized there’s a leg up here for hiring managers as well. We all know that 90% of the great engineering talent isn’t actively on the market at any given time. Instead, they’re building, sharpening their skills … and, for several thousand of them at least, they’re reading this newsletter. Why not meet them where they are, every two weeks, with an offer they can’t refuse? In a newsletter where job ads aren’t mixed in with other stuff, but where they’re the whole point?

Introducing “The Best Jobs in Cloud”

“The Best Jobs in Cloud” is a new add-on to this newsletter that will come out every two weeks on Thursday.

In each issue, I curate awesome cloud job opportunities from around my network, including an inside referral for each job so you can skip the application line.

What do I mean by “the best”? I’ll be using the following editorial criteria when putting this newsletter together:

  • I bias for remote jobs; even better if they are true, global “work from anywhere” remote jobs without a geographical restriction.

  • I bias for jobs that include a salary range (it’s hard to get companies to post these, but I push for it wherever I can).

  • I bias for jobs where I personally know people inside the company and can vouch for the health of the culture and the interesting-ness of the work.

  • I sort the list according to required experience, and I try to make sure I have a healthy balance of junior, mid-level, and senior jobs. (I may use a few sponsored listings to make sure I achieve that balance; don’t worry, the sponsored posts will go through the same editorial criteria as everything else.)

Some of the jobs will look familiar; the big 3 cloud providers will represent, for sure. Others will be with interesting startups you’ve never heard of. All will be excited to hear from you. (If you’re hiring and you want to list a job, just fill out this quick form!) Yes, I really am serious about using the Cloud Resume Challenge to help you get hired.

There’s a $5 /month subscriber cost if you just want the newsletter, mostly to keep my hiring managers from getting too overwhelmed with resumes, but again — you will get this newsletter for free by purchasing the Cloud Resume Challenge book. That’s right: it’s really intended as a free, ongoing add-on to the book, for as long as you need it. I’d argue you need it as long as you work in cloud. It’s always important to know the state of the market, even if you’re not actively shopping for a new role.

Plus, I’m going to send the first issue to the whole newsletter for free, so keep an eye out for that tomorrow. I’d love your feedback on whether it’s useful to you, or what other information you would need to make it worth your while.

To all of you who have contributed to making the Cloud Resume Challenge community a small miracle in tech, thank you. I’m hopeful that these new features will help the mechanics of the challenge scale much bigger than “Forrest’s inbox”. And I can’t wait to see many more of you take the next step in your careers.

Why all the songs?

If you follow me on social media, you may have noticed a surge of little cartoons and songs over the past few weeks. I made these out of joy that I could make them again.

Because just over three months ago - April 2, Good Friday, to be exact - it all almost went away.

I was playing with my kids in the street on a beautiful spring evening. Stomp rockets: little foam darts attached to a hose with a rubber bellows on the end. The kids are five and three. They love to stomp and make Dad chase the rockets as they sail far overhead.

Running backwards after one of these rockets, I felt my feet going faster than my upper body and knew with sudden certainty that I was going to fall backwards. I’m 6’1’ and highly uncoordinated, and I was going fast. Momentum took over before I could get my elbows underneath me.

The back of my head smashed into the concrete curb, rebounded, and whiplashed back again.

If I was unconscious, it was only for an instant. Instead I experienced the strangest sensation of my life. Shock waves reverberated down my spinal column as my body tried to absorb the impact. My spine was literally buzzing, vibrating like an incoming call from my future. My mind was clear: I could hear the footsteps of my children running toward me. But I could not move my arms and legs.

I am twenty-eight years old, and for an endless minute I was not sure if I would move again.

Then, slowly, my muscles began to respond. I rolled over and got up and helped the kids inside (“You’re bleeding, Dad!”) and went to the emergency room.

Just a concussion, they said. No brain bleed. Give it time. For weeks I couldn’t look at a screen, couldn’t work or spend more than a few minutes with my family without blinding headaches. Where my creative juices usually flow, I just felt a dull block of pain. For the first time in my adult life I couldn’t write, couldn’t play or even listen to music, couldn’t do any of the things that I think of as defining me. This was, to say the least, existentially flummoxing.

I was blessed that it wasn’t worse. I am blessed that now, after rest and physical therapy, I can work and create again. But this was not a guarantee. A little different angle, a little sharper curb - who knows. It can happen so fast. Life can change in an instant, no matter your place on the actuarial table or personal health history. There are no guarantees. Enjoy the moments, seize the days. They matter. You matter.

Sing along with me.

Links and events

Tomorrow: CloudFormation Deep Dive

July 22: Pluralsight + ACG Roundtable

Just for fun

Maybe you’re not surprised to learn that I did all this after getting clobbered in the head.

The Ransomware Song (Just Blame Math)

The Elastic Load Balancer Yodel Rag

That Sinking Feeling (The #HugOps Song)

Ode to Infinidash (featured in The Register!)

Probably Wrong Flowcharts: AWS Container Services, AWS Database Services

Loading more posts…