Managing releases can be one of the most tedious aspects of maintaining an Elixir project (or any project). Manually updating version numbers in mix.exs, crafting changelogs, creating GitHub releases, and ensuring consistency across your project can quickly become overwhelming as your project grows. What if we could automate all of that while also improving your development workflow? | elixirschool.com
Struggling with backend career growth? This 2025 guide is your strategic roadmap to master essential skills, tech, & practices for faster advancement.| strategizeyourcareer.com
People should try to compare the quality of the kernel git logs with| tylercipriani.com
How to write a good commit messages that actually helps my future self to understanding previous code-changes so that I can fix bugs easily| andreas.heigl.org
At least not before reading this!| Lucas Seiki Oshiro
A set of rules, their rationale and a short practical guide to creating useful commits.| Bence Ferdinandy
Releasing Rust packages is tedious and error-prone, just like most IT manual tasks. For every package you want to release, you need to: Increase the version in Cargo.toml. Update the changelog.| www.marcoieni.com
Every now and then, at work, I find myself discussing git worfklows, commit messages, branching, releasing, versioning, changelogs etc. Since my opinion has remained fairly consistent for the past few years, I found myself repeating the same points a lot, so I wrote it down. This page is the resulting compilation of my opinions on the software development lifecycle (SDLC), without workplace-specific tangeants. The article is broken down into ideas + recommendations, with recommendations in bold.| jiby.tech
In this article, we introduce a framework for balancing engineering investments across four categories and explain how to get started.| www.swarmia.com
