Corey Quinn

There’s a universal lie that technical people believe across the board. It goes something like this: “After this next sprint ends, then we’re going to pay off all of our technical debt and start doing everything the right way.”

I’m afraid I come to you this morning with terrible news: I’ve been writing code again.

I once said that AWS has launched so many services that I could talk about a service that didn’t really exist and not get called out for it–by AWS employees. Sure enough, last week saw the rise of AWS Infinidash, an imaginary AWS service that doesn’t (at the time of this writing) really exist.

Back in March, I took the beta AWS Certified Sysops Administrator – Associate exam because my Certified Cloud Practitioner was expiring.

There’s a joke that I’ve always been partial to: a software engineering type rubs a lamp and a genie appears. The genie says that he’ll grant the engineer $1 billion, but only if they can spend $100 million in a single month with three rules. “You can’t gift it away. You can’t gamble with it. […]

A couple of weeks ago, a blog post from Andreesen Horowitz talked about “The Cost of Cloud, a Trillion Dollar Paradox.”

When you talk about AWS billing, you’re talking about AWS architecture. Most folks don’t recognize that they’re the same thing.

Before you buy Savings Plans, sign an AWS contract, or rearchitect your environment, consider doing this first.

There may be 50 ways to leave your lover, but there are 17 ways to run containers on AWS. I will now enumerate them.

Adam Selipsky is returning to AWS as its new CEO. I fill him in on some of the things he missed while he was gone.

If you attend an AWS talk about security, bump into an AWS security person in a business meeting, or are in line behind an AWS employee at a Starbucks, you’ll invariably hear the phrase “Security is Job Zero.” What does this actually mean? Cynically, I might suggest that they came up with a list of […]

Developer portals can be used to enforce standardization and to enable multi-cloud use cases. But they also have some serious issues and should be avoided in most cases.