Team resistance to modern coding standards
🧭 worksocial problemSingle report ●●●●●
A team lead reports that their team members, who have backgrounds in C and Java, are resisting the implementation of modern C++14 coding standards and best practices, leading to conflict and stalled progress on a new feature.
What people do today
- Linking to language core guidelines in merge requests
- Creating a custom coding convention document
- Holding weekly team votes on which recommendations to follow
🔧 Fix this
Ideas a builder, maker or community group could start on:
- A structured workshop series that demonstrates the tangible performance or safety benefits of specific C++ idioms compared to older C-style approaches.
- An automated linting tool configuration that enforces agreed-upon standards to remove the personal nature of code review feedback.
- A team charter template that helps leads and developers negotiate a 'middle ground' coding standard that balances modern practices with team velocity.
Real voices
“one guy (call him 'John') expressed very strong resistance to my recommendations. He claimed that these are just recommendations and not rules”
Related problems
🧭 workproduct6 reports
LinkedIn login verification loop
🧭 workproduct6 reportsInability to filter AI-generated content on LinkedIn
🧭 workproduct6 reportsIndeed job feed ignores user preferences
FixHumanityDaily
The most important new problems, and ideas to fix them, in your inbox.
Placeholder: no data is collected yet.