With all the (justifiable) hate on microservices recently, I think it is important to point out that if your organization couldn’t establish the engineering processes and discipline to do them well then going serverless is going to explode your problems 10-100x.

This is you going serverles on your environment without a proper emphasis on education, training, and skilling.

“So we turned even Hello World into a distributed application, and now the living envy the dead.”

When you see other people using a technology well, maybe the problems are in the people and processes? 1/4

Which begs the question whether or not you have the right people and processes? 2/4

Which begs the question whether you need those people and processes? 3/4

Which begs the question whether you or not you need that technology? 4/4

Serverless will be the biggest LOL fuck you on developers since full stack. They think they‘re buying into only having to focus on code and not infrastructure, but instead we are secretly turning them into distributed systems engineers more than developers.

Don’t take this thread for me hating on serverless. Because I freaking love it.

An absolute hack of an ops person like me can write a decent backend service now!

You actually just made my skills way more relevant so long as I make the choice to transition more towards dev work.

But if we aren’t honest with devs about the changes to their work they will face in adopting serverless, there will be a backlash.

The work won’t be what they thought they signed up for or they haven’t developed the practices to build systems that don’t break regularly.