typo, thx Luk

This commit is contained in:
Wouter Groeneveld 2021-05-31 18:07:04 +02:00
parent d6539598d8
commit e4e9040eee
1 changed files with 1 additions and 1 deletions

View File

@ -14,7 +14,7 @@ We software developers talk about code smells all the time. We organize working
## From technical to social debt
Technical debt might be annotated with `@TechnicalDebt` in code---I've seen it happen and then happily ignored---but what about social issues in development teams? We all know it severely effects team performance---perhaps orders of magnitude more than a few "simple" code smells you have to work around (or, hopefully, fix). We also all implicitly know a couple of **community smells**: just like code smells, they're anti-patterns that emerge time and time again in (development) communities and negatively effect what the team is trying to accomplish.
Technical debt might be annotated with `@TechnicalDebt` in code---I've seen it happen and then happily ignored---but what about social issues in development teams? We all know it severely affects team performance---perhaps orders of magnitude more than a few "simple" code smells you have to work around (or, hopefully, fix). We also all implicitly know a couple of **community smells**: just like code smells, they're anti-patterns that emerge time and time again in (development) communities and negatively effect what the team is trying to accomplish.
I really like the terms "social debt" and "community smells", as they perfectly accompany their more well-known counterpart "technical debt" and "code smells". I encountered these words in Damian Tamburri's papers, where he talks about the "shepherding" role of the software architect (or team/devlead, for that matter), who is a negotiator that should try to minimize the effects of both kinds of smells.