Is Trunk Based Development still a nightmare? 🚀 - Issue #6

Here we go, welcome to the issue number 6️⃣! 🚀

Just a shout-out about an accomplishment I’ve made: last week, I received my first donation through https://ko-fi.com/dlion 🎉

Someone discovered my article about Web Scraping with Rust, found it helpful and thought to offer me a coffee ☕️; I’m so happy to know that my work somehow has been valuable for someone else 🙏

Integrating often and directly on master can be scary, especially initially, but the benefits are uncountable over time. ⏰

This approach is called: Trunk Based Development.

Integrating frequently helps you have faster feedback ⚡️, avoid big merges 💥, and force you to run your test suite every time 🥅, providing to your colleague the latest version of the code as fast as possible 👫. Those are just a few points. You can find lots of information about this approach and how to avoid anti-patterns on this website. 👀

I’ve always been a big fan of writing journals at the end of the day. 📝

It helped me remember what I’ve done right after the weekend or helped my colleagues to stay up to date on my task, recording what problems I encountered and how to solve them.

So why don’t we apply this concept to our architectural decisions?

Recently, I had to conduct some user testing research remotely, and I found this article super interesting. Have you ever conducted user testing interviews in the past? How did you change your approach to run them remotely?

I recently found a very small nice chart about databases scalability, I found it very helpful to understand in a blink of an eye the differences between replication and sharding. 💡

Thank you for reading and see you in the next issue ☄️