Software Systems can easily pile up technical debt (see my Clean Architecture for more thoughts on that). One of the reasons is that people rush. Another common one is not thinking about or knowing about good software practices.
How do we teach this and rely the concepts? I don’t think a style guide and coding standards is enough, but I offer some principles to follow and share.
"Haste makes waste"
Upgrade Nuget packages when you add new code
build time analyzers SonarQube/NDepend
Teaching takes time and effort. We all need to learn humbly from each other.
I think that Pull requests are an easy first step. Pair programming and working together is another good way. We need to hold each other accountable to create better code (or delete bad code) that’s readable, maintainable and sustainable.
I also suggest lunch and learns and book groups.
Keep learning and improving.
There is much more that should be added and I’m sure I’ll come back and add more in the future as I think of more. I’m sure you have ideas, please let me know in the comments.
Please consider using Brave and adding me to your payment ledger. Then you won't have to see ads!