Development Practices

Tips for making changes to third-party dependencies and contributing them upstream, using npm and git—though you can use other languages' packaging systems.

We need to stop taking a sprint to "deal with tech debt," and start taking time to "implement the lessons we've learned over the past X sprints."

Write error messages that won't make readers think. A good error message should both point out a problem in your code and indicate a solution.

Use your relational database management system to its full potential to process data, describe domain logic, and take action when data changes.

There are real costs involved in the decision to have a development team work in multiple repositories—I believe these costs are always overlooked.