Activity, over time
Daily observations from the public event archive.
Attention
Daily stars & forks
Star accumulation
Cumulative stars
Pull requests
Daily opens & merges
Conversations
Daily issues & comments
Community
Daily accounts & reviews
Releases
Daily releases
Trending history
Daily top 10 · last 90 days · UTC
Mentions
Stars
Forks
Contributors
Latest stargazers
The last 10 distinct accounts we observed this year.
Most active participants
PR, issue, comment & review events in the past year.
Packages
| Package | Version | Downloads · 30d | Trend · 30d |
|---|---|---|---|
| — | — | — | |
| — | — | — | |
dispatchv2.0.6 | v2.0.6 | ≥694 |
README badges
Embed a badge in your README or website.
Live mentions · last 30 days
Mentions
@Swizec you can actually read every line. its not hard when the code is readable. i keep posting this example to folks (it might not be the best-architected, but oh wow is it readable) - Netflix/dispatch
@thorstenball Code is the complete source of truth. Explainer maps are supplemental. Labs need to address the problem and make the agent write readable code like e.g. this repo: netflix/dispatch and we need to stop pretending the issue is not real because we can cleverly work around it.
@icanvardar I can show you an example of readable code: Netflix/dispatch