Architecture Weekly Issue #6. Articles, books and playlists on architecture and related topics. Every record has the complexity indication: 🤟 means hardcore, 👷‍♂️ is technically applicable right away,  🍼 - introduction to the topic or an overview.

WARNING

Russia invaded Ukraine this week. We condemn this invasion. The war is awful, unjust and in particular case has zero reasons. We feel for Ukranians hurted by this inhuman act. Meanwhile we believe that professional development is not out of agenda and we continue to put effort in this newsletter.

Better writing 🍼

Architects should write a lot: manuals, decision records, letters, discussions. Writing is a critical skill. Amazon cultivates it's writing culture for years. A good article on how to improve your writing.

Becoming a Better Writer as a Software Engineer
Writing is an increasingly important skill for engineering leaders. Indeed, poor writing can hamper career progression, above a certain level. Tactics for more clear, more frequent and more confident writing. I’ve observed that my writing is not up to par with my peers. How can I improve my professi…
The Pragmatic EngineerGergely Orosz

Stop using branches for different environments 👷‍♂️

Several years ago I used gitflow and created separate branches to deploy to staging and production. This practice is dying out and it should. Kostis Kapelonis explains why it's considered bad practice.

Stop Using Branches for Deploying to Different GitOps Environments
In our big guide for GitOps problems, we briefly explained (see points 3 and 4) how the current crop of GitOps tools don’t really cover the case of promotion between different environments or how even to model multi-cluster setups. The question of “How do I promote a release to the next environment?…
Kostis Kapelonis