What technical debt actually is, how to distinguish debt worth paying from debt worth ignoring, and how to make the case for cleanup work to a non-technical stakeholder.
A commit is not a diff - it is a snapshot. Understanding the object model inside .git/objects changes how you think about branches, merges, and history.
A commit message is a letter to whoever debugs this code next. Here is how to write one that actually helps.
Most teams argue about Gitflow vs trunk-based development. The better question is what you are actually trying to solve.
A code review is not a gatekeeping exercise. Here is what makes them useful - from both sides of the diff.
Refactoring is changing structure without changing behavior. The hard part is keeping those two things separate.
