summaryrefslogtreecommitdiff
path: root/Biz/Dragons/pitch.md
diff options
context:
space:
mode:
Diffstat (limited to 'Biz/Dragons/pitch.md')
-rw-r--r--Biz/Dragons/pitch.md40
1 files changed, 40 insertions, 0 deletions
diff --git a/Biz/Dragons/pitch.md b/Biz/Dragons/pitch.md
new file mode 100644
index 0000000..a4d4ffa
--- /dev/null
+++ b/Biz/Dragons/pitch.md
@@ -0,0 +1,40 @@
+# Dragons
+
+Dragons 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. Dragons 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, dragons 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? Dragons analyzes the collaboration patterns between devs and helps
+you form optimal pairings and teams based on shared code and mindspace.
+
+(Paid only)