diff options
| author | Ben Sima <ben@bsima.me> | 2020-12-04 11:16:25 -0500 |
|---|---|---|
| committer | Ben Sima <ben@bsima.me> | 2020-12-05 07:55:13 -0500 |
| commit | 330e4363d8abb509031d2c8c1a89dcc6f955e2c1 (patch) | |
| tree | 915c8c50a7125bf6eb9e560f8d00a80592f41c77 /Devalloc/pitch.md | |
| parent | 32f53350a3a3d701e9a1474e670a8454342adc40 (diff) | |
Renamespace Devalloc and Que
Move them under the Biz root so that we know they are specific to Biz stuff. Biz
is for proprietary stuff that we own.
I also had to refactor the bild namespace parsing code because it couldn't
handle a namespace with 3 parts. I really need to get that namespace library
written and tested.
Diffstat (limited to 'Devalloc/pitch.md')
| -rw-r--r-- | Devalloc/pitch.md | 40 |
1 files changed, 0 insertions, 40 deletions
diff --git a/Devalloc/pitch.md b/Devalloc/pitch.md deleted file mode 100644 index cfc0b23..0000000 --- a/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) |