3 ms·
* Jira for work allocations with a solid source control integration. On the human side, a well defined structure to how branches/commits/merges must operate. *
by el_dev_hell 6y ago
* Jira for work allocations with a solid source control integration. On the human side, a well defined structure to how branches/commits/merges must operate.
* Code formatting. A decision is made and everyone follows (by force from the formatter) a single formatting methodology. In JavaScript land, Prettier is great. Python has Black, which is alright. The biggest benefit is making code reviews easier.
* A standing desk raiser. I would prefer a walking desk, but I haven't made time to set it up.
- nicbou 6y agoCode formatting is really important. Things got marginally better once we agreed on the AirBnB coding standards at my old company. It allowed us to focus on more important things during reviews. In other teams, I also implemented similar filters for commit messages, enforcing ticket numbers in messages (or tags like "hotfix"). I learned the latter from refactoring a lot of code with seemingly unexplained business logic. At least now I could trace it to a business requirement. It also made reviews easier. All of these can be added to git hooks.