Thread by @PaulDJohnston

Increasingly thinking that the reason that I go on and on about serverless best practices and principles is that I don't care about technology that much, but culture.

Because instilling the right culture is much more likely to produce great tech.

I'm not averse to coding up solutions where necessary.

It's simply that with the proliferation of cloud based services, and solutions that you can get off the shelf...

... why would you?

Unless you had a specific business critical reason, then you are wasting time and money.

And understanding the technologies that you have available to you is a key part of utilising them to your advantage.

So doing that due diligence is key as well. Assuming that you understand it because it looks like something else is laziness.

Know your tools!

I'm a great believer in getting developers and teams to back up their ideas with business reasons. If a team comes with an idea, that is outside the current scope of what we do, then ask for a business reason to do it.

It's amazing what solutions can be found within constraints

Having a set of principles for the tech part of your organisation isn't straight forward, but it is necessary. Most that I've seen simply focus on short term development goals as the metrics. The ones that succeed have a much longer term focus and clear shared principles.