diff options
| author | Ben Sima <ben@bsima.me> | 2021-08-23 13:06:15 -0400 |
|---|---|---|
| committer | Ben Sima <ben@bsima.me> | 2021-11-26 13:47:38 -0500 |
| commit | 45f352f9cb3bdc16048a0f0d70eef6a59272472b (patch) | |
| tree | 7cae4b608e45360085d950d7c14d80911ce46b7c /Biz/Dragons/pitch.md | |
| parent | aa2eb2d3e08fb74b93acc9608a78582834a65e8c (diff) | |
Fix GitHub OAuth args
This makes it explicit that we are using GitHub vs some other OAuth args. The
idea is that we should be making a new type for every service, this allows us to
have type safety in the implementation but a common set or pattern of names for
the environment variables and record fields.
Also using 'notset' instead of 'mempty' is really helpful for debugging when
this breaks, as I found out.
Diffstat (limited to 'Biz/Dragons/pitch.md')
| -rw-r--r-- | Biz/Dragons/pitch.md | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/Biz/Dragons/pitch.md b/Biz/Dragons/pitch.md index a4d4ffa..91352fc 100644 --- a/Biz/Dragons/pitch.md +++ b/Biz/Dragons/pitch.md @@ -1,6 +1,6 @@ -# Dragons +# Dragons.dev -Dragons analyzes your codebase trends, finds patterns in how your developers +Dragons.dev 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. @@ -9,15 +9,15 @@ Just hook it up to your CI system - it will warn you when it finds a problem. 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 +tech debt. Dragons.dev 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. +that only 1 or 2 people have touched, Dragons.dev 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" @@ -34,7 +34,7 @@ developers then you will never get optimal performance from your team. ## 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 +together? Dragons.dev analyzes the collaboration patterns between devs and helps you form optimal pairings and teams based on shared code and mindspace. (Paid only) |