I recently had the pleasure of being a guest on my friend and fellow Belfast resident Marco Troisi’s new podcast “The Serverless Mindset”.
Highlights from our chat:
- Best practices should be thought of as rules of thumb: they should be followed but it’s ok not to follow them if you have a good reason not to
- Context is key: who, what, and why was a best practice created? This is crucial, since it may not apply in your specific context
- Serverless is a radically different paradigm, so we are justified in not taking previously accepted best practices for granted
It’s quite a short episode (17 mins) and you can listen to it here.
You might also want to check out Marco’s excellent Serverless Mindset newsletter where he publishes new articles every week on topics such as testing, vendor lock-in and microservices.
I’ve also published several daily emails since my last message to you. Here’s a selection of posts that sparked some discussion:
- Why monolithic deployments make sense for small serverless teams
- It depends on your organisational context
- DevOps practices for small serverless teams
- Handling future changes to your DynamoDB access patterns
- My development workflow for implementing a feature in an AppSync project
- A minimal set of documentation for your serverless project
- Use SSO instead of IAM users to connect to your AWS accounts
- Local development is an XY problem
- Deciding on what environments to create for a serverless team
- How to continually integrate WIP features for your serverless app
- When prototype becomes production
- Focus your code reviews on identifying hard-to-change-later items
Indie Cloud Consultant helping small teams learn and build with serverless.
Learn more how I can help you here.
Join daily email list
I publish short emails like this on building software with serverless on a daily-ish basis. They’re casual, easy to digest, and sometimes thought-provoking. If daily is too much, you can also join my less frequent newsletter to get updates on new longer-form articles.