Teams can have more effective code reviews if they default to approval and have a framework for delivering and managing feedback.
Standups are often applied without understanding the problem they are solving. This leads to:
1. Not clearly solving a specific problem
2. Not solving a problem with the best solution
3. A daily interruption to deep work
What follows is a pragmatic and ideal approach to resolving this situation. The pragmatic approach is to understand so you can excel within that system. The ideal solution tries to change the system to better serve the team.
The term Manager means a lot of different things to different companies. It can include Project Manager, Product Manager, Technical Lead, Team Lead, Mentor, Coach, Supervisor, as well as Individual Contributor. Most often, in my experience, a manager is responsible for at least these roles: Supervisor, Mentor, and Team Lead.
There is great value in having those roles played by separate people.
Melanie Sumner and I wrote about the Six Pillars of Accessibility as a structured guide for developers to move the needle on accessibility.
- User Experience
- Visual Design
I have gone through the process of adding linting to existing, large projects a couple of times. I've learned some lessons about how to approach this so that it's not disruptive to the team doing other work. Follow these steps to get robust linting into your project without pulling team velocity to a halt!