summaryrefslogtreecommitdiff
path: root/Biz/Devalloc/pitch.md
diff options
context:
space:
mode:
authorBen Sima <ben@bsima.me>2021-08-18 13:25:31 -0400
committerBen Sima <ben@bsima.me>2021-11-26 13:47:37 -0500
commit1176a24a1f76f551ec32eda731e8d5cdf93ad085 (patch)
tree69d6ead8e57e54f2886808769a134d57b2e0893d /Biz/Devalloc/pitch.md
parent2462d2c1377b645a99cba38875628b18d7da5ac8 (diff)
Rename Devalloc to Dragons
Diffstat (limited to 'Biz/Devalloc/pitch.md')
-rw-r--r--Biz/Devalloc/pitch.md40
1 files changed, 0 insertions, 40 deletions
diff --git a/Biz/Devalloc/pitch.md b/Biz/Devalloc/pitch.md
deleted file mode 100644
index cfc0b23..0000000
--- a/Biz/Devalloc/pitch.md
+++ /dev/null
@@ -1,40 +0,0 @@
-# Devalloc
-
-Devalloc analyzes your codebase trends, finds patterns in how your developers
-work, and protects against tech debt.
-
-Just hook it up to your CI system - it will warn you when it finds a problem.
-
-## Identify blackholes in your codebase
-
-What if none of your active employees have touched some part of the codebase?
-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.
-
-## Protect against lost knowledge
-
-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.
-
-## Don't just measure "code coverage" - also know your "dev coverage"
-
-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.
-
-- Find developer "hot spots" in your code: which pieces of code get continually
- rewritten, taking up valuable dev time?
-- Know how your devs work best: which ones have depth of knowledge, and which
- ones have breadth?
-
-(Paid only)
-
-## See how your teams *actually* organize themselves with cluster analysis
-
-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.
-
-(Paid only)