Issue #9

Hello CloudMakers!

I hope it is a pleasant start of the year for you, and that the return to work was not too traumatic 😅 for my part, I am recovering from a fortunately mild Covid, which nevertheless gave me plenty of free time to read and get new ideas ✨

In fact, today's issue includes three interesting articles plus one written by me - whether it is also interesting is up to you to say!

We shall see:

  • the developer experience as a top priority in 2023, with a focus on integrated DevOps/Platform Ops teams

  • database change management like a Boss DevOps 😎

  • plenty of ideas to become an open-source contributor

  • BONUS: my practical implementation of Continuous Delivery and GitOps 🚀


Platform Engineering in 2023: Dev First, Collaboration and APIs

The focus on the developer experience will continue to grow in importance in 2023, and the trend of using developer platforms to improve this experience and support operational efforts through "Platform Ops" will continue. The integration of DevOps and Platform Ops teams will also become a business-critical requirement as cloud-first development becomes more widespread.

How to bring DevOps to the database with GitLab and Liquibase

When you're releasing new code, you want to make sure that everything is under control - but what about the database? Proper database change management involves tracking and controlling changes to the database to minimize risk and ensure that your software is running on a consistent and up-to-date version of the data. Not to mention its importance for a rollback... Let's see how to implement proper database change management with Liquibase!

How can I become an Open Source contributor? (The ultimate guide)

There are several benefits to becoming an open-source contributor, including learning and improving skills, building a portfolio, giving back to the community, and having a fun and rewarding experience. Not sure where to start? We've got you covered.

BONUS: Continuous Delivery for the rest of us 🤓

Several times in the last few months I've worked on projects where I'm trying to find a way to effectively use automation to deploy code in multiple environments, while still being able to meet specific timing constraints and not altering release candidates. The solution I've found combines continuous integration with GitOps practices to achieve continuous delivery, which allows you to go from committing code to deploying it in a development environment while still being able to manage releases in different environments at different times. Hope you'll like it!

Thank you for reading my newsletter!

If you liked it, please invite your friends to subscribe!

If you were forwarded this newsletter and liked it, you can subscribe for free here:

Have you read an article you liked and want to share it? Send it to me and you might see it published in this newsletter!

Interested in old issues? You can find them here!

Until next time!