diff options
| author | Ben Sima <ben@bsima.me> | 2020-09-29 13:31:07 -0400 |
|---|---|---|
| committer | Ben Sima <ben@bsima.me> | 2020-09-30 13:33:35 -0400 |
| commit | b040aed9e904d3ec683810422f3b4d9151c7312a (patch) | |
| tree | e4646b8ec780396acfdfcdba2beea5a7c77e7abf /Devalloc | |
| parent | babb2fdc69bb0d777e72072d3509eeed4c1b651d (diff) | |
devalloc: make a simple sales pitch document
Diffstat (limited to 'Devalloc')
| -rw-r--r-- | Devalloc/pitch.md | 42 |
1 files changed, 42 insertions, 0 deletions
diff --git a/Devalloc/pitch.md b/Devalloc/pitch.md new file mode 100644 index 0000000..3d122b4 --- /dev/null +++ b/Devalloc/pitch.md @@ -0,0 +1,42 @@ +# Devalloc + +Devalloc is a service that analyzes your codebase trends, finds patterns in how +your developers work, and protects against tech debt. + +This pre-release prototype is a script you can download and freely run on your +git repo (requires Python >=3.6). The next, paid version of Devalloc will have +an API, easy connectors to common CI systems, and automated reporting. + +## 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? + +(Available in future paid service) + +## 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. + +(Available in future paid service) |