Open Source
Choosing an open-source license: a plain-language guide
Code without a license isn't open source, even if it's public. Here's how the major license families differ and how to pick one.
Editors
Editorial Team
The software-devs editorial desk.
Open Source
Semantic versioning: what the three numbers promise
MAJOR.MINOR.PATCH is a contract between library authors and users. Understanding it helps you upgrade safely and publish responsibly.
Open Source
Writing a README people actually read
Your README is your project's front door. Answer the first three questions every visitor has, and keep the rest a click away.
Tools
Code review etiquette for authors and reviewers
Good reviews catch bugs and spread knowledge without bruising anyone. Small habits on both sides of the pull request make the process faster and kinder.
Open Source
Keeping a changelog humans want to read
A git log is not a changelog. A short, curated record of notable changes tells users what an upgrade means for them.
Tools
A modern command-line toolkit for developers
A handful of fast, focused command-line tools can replace minutes of clicking every day. Here's a starter kit and how the pieces combine.
Tools
How to write commit messages your future self will thank you for
A commit message is a note to whoever runs git blame next year. A few conventions make history searchable and debugging faster.
Tools
Talking about technical debt so the business listens
Saying "we need to refactor" rarely wins a planning meeting. Framing debt in terms of risk, speed and cost does.
Tools
Monorepo or polyrepo? The trade-offs, honestly
Whether to keep all your code in one repository or many is mostly a question of tooling and team structure. Neither is free.
Tools
Debugging methodically: treat bugs like experiments
Random changes and hopeful restarts waste hours. A scientific approach — reproduce, hypothesize, test, narrow — finds bugs faster.