少なく返せば、軽くなる?
GitHub
@githubOct 14
⭐ We shaped our new repo star history API around production evidence and maintainer feedback. Now it provides trends without returning individual identities or requiring unbounded database work. The practical engineering tradeoffs that made it happen ⬇️
15
Michael Taiwo
@AskMichaelTaiwoOct 15
If I want to know how many people completed an application, I don't need to export their names into another tool. Decide what the report needs before moving the data.
GitHub
@githubOct 14
⭐ We shaped our new repo star history API around production evidence and maintainer feedback. Now it provides trends without returning individual identities or requiring unbounded database work. The practical engineering tradeoffs that made it happen ⬇️
3
3
3,031
Tellus Cooperative 🌎
@TellusCoopOct 15
Historial de estrellas sin doxxear a nadie ⭐ @github rediseñó su API de star history: tendencias del repo sin devolver identidades individuales ni tumbar la base de datos. Ingeniería práctica para maintainers. Vale la pena el hilo.
GitHub
@githubOct 14
⭐ We shaped our new repo star history API around production evidence and maintainer feedback. Now it provides trends without returning individual identities or requiring unbounded database work. The practical engineering tradeoffs that made it happen ⬇️
1
100
xitter.cf/github/status/21104908… ده مثال ممتاز لتصميم Metric من غير ما يتحول لمراقبة أفراد أو استعلام بلا حدود. نفس المبدأ ينفع في PMO dashboards: اعرض الاتجاه والقرار المطلوب، اخفِ البيانات الشخصية، وحط تكلفة وحدود واضحة لكل مؤشر.
GitHub
@githubOct 14
⭐ We shaped our new repo star history API around production evidence and maintainer feedback. Now it provides trends without returning individual identities or requiring unbounded database work. The practical engineering tradeoffs that made it happen ⬇️
76
There are many repos with tons of stars, but most of those stars are fake. GitHub needs to identify which repos have paid for stars.
GitHub
@githubOct 14
⭐ We shaped our new repo star history API around production evidence and maintainer feedback. Now it provides trends without returning individual identities or requiring unbounded database work. The practical engineering tradeoffs that made it happen ⬇️
1
28
We love improvements like this! Staying within GitHub's API rate limits is everything for us. And it means we can push performance even further
GitHub
@githubOct 14
⭐ We shaped our new repo star history API around production evidence and maintainer feedback. Now it provides trends without returning individual identities or requiring unbounded database work. The practical engineering tradeoffs that made it happen ⬇️
5
135