diff options
Diffstat (limited to 'Biz/Devalloc.hs')
| -rw-r--r-- | Biz/Devalloc.hs | 9 |
1 files changed, 6 insertions, 3 deletions
diff --git a/Biz/Devalloc.hs b/Biz/Devalloc.hs index df90c9e..a16803b 100644 --- a/Biz/Devalloc.hs +++ b/Biz/Devalloc.hs @@ -870,14 +870,17 @@ instance Lucid.ToHtml Home where \ This happens too often with legacy code, and then it turns into a huge source of tech debt. \ \ Devalloc finds these \"blackholes\" and warns you about them so you can be proactive in eliminating tech debt." section <| do + h2 "Find developer hot spots" + p + "Which pieces of code get continually rewritten, taking up valuable dev time? \ + \ Find these module hot spots before they becoming a cost-sink." + section <| do h2 "Protect against lost knowledge" p "Not everyone can know every part of a codebase. By finding pieces of code that only 1 or 2 people have touched, devalloc identifes siloed knowledge. This allows you to protect against the risk of this knowledge leaving the company if an employee leaves." section <| do h2 "Don't just measure code coverage - also know your dev coverage" p "No matter how smart your employees are, if you are under- or over-utilizing your developers then you will never get optimal performance from your team." - Lucid.ul_ <| do - Lucid.li_ "Find developer hot spots in your code: which pieces of code get continually rewritten, taking up valuable dev time?" - Lucid.li_ "Know how your devs work best: which ones have depth of knowledge, and which ones have breadth?" + p "Know how your devs work best: which ones have depth of knowledge, and which ones have breadth?" section <| do h2 "See how your teams *actually* organize themselves with cluster analysis" p "Does your team feel splintered or not cohesive? Which developers work best together? Devalloc analyzes the collaboration patterns between devs and helps you form optimal pairings and teams based on shared code and mindspace." |