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
Scan pending.
README badges
Embed a badge in your README or website.
Live mentions · last 30 days
Mentions
- My own Robot Simulator entry for one of the contests on BadCode.rocks. I fulfilled the prompt of “the worst working implementation to the challenge that [I could] devise” and won an Honorable Mention. - Along the same lines, the better-known FizzBuzzEnterpriseEdition satirically uses a large framework to solve a simple problem. - Quine Relay does something useless but complex in a way that was obviously hard to build. - The winners of the Underhanded C Contest contain hard-to-find bugs that undermine the program’s purpose but look like accidents after they’re found. More generally, Improv Everywhere’s 2009 Subway Art Gallery demonstrated to me that “art” is a perspective with which one can view any object, so I think it’s never wrong to call something “art”. But I find more artistic value in works that satisfy challenging contraints. The most common source of artistic value in programs is the way their code was optimized to be easily readable and maintainable by a human while still implementing the required behavior.