Pretty cool idea. When I type in my Github name (queicherius) and choose any year however, "february" shows up twice: http://i.imgur.com/MrI9r6a.png
Show HN: Posters of Your GitHub Contributions
71–80 of 80 posts
Re: Show HN: Posters of Your GitHub Contributions
#72I like the idea a lot! I wish there were several ways of visualizing activity so that you might get a more accurate representation of achievement, although that feedback is for github. I like the logo - it's a simple design that represents that product well.
Re: Show HN: Posters of Your GitHub Contributions
#73Pretty cool idea. When I type in my Github name (queicherius) and choose any year however, "february" shows up twice: http://i.imgur.com/MrI9r6a.png
Sorry about that, should be fixed now. Was having some pretty serious issues yesterday.
Re: Show HN: Posters of Your GitHub Contributions
#74Earlier quoted context omitted.
> GitHub has very little secret sauce here GitHub's secret sauce was to use dark patterns meant to accelerate the network effect working in their favor. Specifically: 1. Quietly kill patches as the main currency in open source 2. Redefine "pull request" to mean "the thing that happens when you click a certain button on github.com" The end result is that collaborating with GitHub-hosted projects is made arbitrarily di…
How did they "kill patches"?
Well, when is the last time you (or anyone else) ever submitted a patch through GitHub? Answer: never. Check out the lengths the Git project itself has to go through to work around the busted GitHub-style pull request mechanism GitHub invented.
Re: Show HN: Posters of Your GitHub Contributions
#75I like the idea a lot! I wish there were several ways of visualizing activity so that you might get a more accurate representation of achievement, although that feedback is for github. I like the logo - it's a simple design that represents that product well.
Thanks humming! I'm glad you like the logo, it just came to me right before I launched. Very pleased with how it turned out.
Re: Show HN: Posters of Your GitHub Contributions
#76Hey yall, looks like it's being hugged to death right now... I'm trying to keep up!
Hey, great work! Similar to my project https://commits.io Shoot me an email (ortuna AT gmail) if you want to compare notes. I've done a lot of work on how to get those generation times down.
Cool service! I had fun playing with the generator but have no intention of ordering a poster.
Recommendation: Allow users to generate an image and either share it on social media, or embed it in their blog. This way you at least get promotional value out of customers who do not intend to buy.
Re: Show HN: Posters of Your GitHub Contributions
#77I think the site is nice - it's clean and directly to the point. No huge hero and no click-throughs to get to the meat of your project. Prices for your posters seem entirely reasonable. Tangent: I don't understand the fascination with one's own commit heatmap (or any other commit heatmap for that matter). Maybe it seems a bit too self-congratulatory? Vain? I don't know quite what it is, but it rubs me the wrong way a…
> or any other commit heatmap for that matter The problem with heatmaps and how they are currently used by popular tools, is they only provide novelty metrics. That is, metrics that are interesting to look at and nothing more. Commit heatmaps are actually quite useful for answering a lot of questions, if used properly. Here's an example, that shows how they can be used to help you navigate to the first commit. https:…
This is pretty interesting, but I don't know how useful it would be for me. Part of why I feel that way would be just because I don't have those use cases.
I guess part of it is I don't use GitHub as a UI to my repos either. When I want to find this information out I go exploring with log/blame.
Re: Show HN: Posters of Your GitHub Contributions
#78Earlier quoted context omitted.
> or any other commit heatmap for that matter The problem with heatmaps and how they are currently used by popular tools, is they only provide novelty metrics. That is, metrics that are interesting to look at and nothing more. Commit heatmaps are actually quite useful for answering a lot of questions, if used properly. Here's an example, that shows how they can be used to help you navigate to the first commit. https:…
This is pretty interesting, but I don't know how useful it would be for me. Part of why I feel that way would be just because I don't have those use cases. I guess part of it is I don't use GitHub as a UI to my repos either. When I want to find this information out I go exploring with log/blame.
The heatmaps and the graphs in general, or more to help you orient yourself, when having to deal with a lot of information. They make it very easy to view activity across multiple files, branches and repos at once.
For me personally, I mainly stick with the "Changes tree", which I prefer to use over log/blame. I'm particular not a fan of using blame, if I need to trace the history for a file, since it can get disorienting. I use what I've dubbed as rapid diffing, which makes it easier to see how a file evolved. Here's an example.
Re: Show HN: Posters of Your GitHub Contributions
#79Earlier quoted context omitted.
How did they "kill patches"?
Well, when is the last time you (or anyone else) ever submitted a patch through GitHub? Answer: never. Check out the lengths the Git project itself has to go through to work around the busted GitHub-style pull request mechanism GitHub invented.
Well, that seems to me to be because they provided an alternative to patches that works a lot better for me and the projects I contribute to, and I can't blame them for it.
Re: Show HN: Posters of Your GitHub Contributions
#80Earlier quoted context omitted.
Well, when is the last time you (or anyone else) ever submitted a patch through GitHub? Answer: never. Check out the lengths the Git project itself has to go through to work around the busted GitHub-style pull request mechanism GitHub invented.
Well, that seems to me to be because they provided an alternative to patches that works a lot better for me and the projects I contribute to, and I can't blame them for it.
[deleted]