Live data from Hacker News

Redesigning GitHub Repository Page

tonsky.me

161–170 of 315 posts

Re: Redesigning GitHub Repository Page

#161

But maybe it’s time to fresh it up a little? Get rid of gradients, dirty washed-out colors, unnecessary separators, add a little more air. No, no, no , NO!!!11 I've had it with these "sea of floating text on an expanse of white" redesigns, seeing yet another one follow this mindless trend just disgusts me thoroughly. The lines, subtle gradients, and other affordances of the old design serve to organise and direct you…

I thought some of his suggestions were pretty decent. But then he just threw everything away by mucking around in the Code, I mean Overview tab. His last design, without the guiding lines, make it look like jumbled shit pie.

Re: Redesigning GitHub Repository Page

#162

First half of the article that redesigns the navigation is actually pretty good. It got me hooked and i find it valuable. When they started touching the content, I got a lot more hesitant. 1. I can't articulate why , but honestly it's extremely useful to see the last commit message on each file. It gives me a sense of which files have changed and if my changes are still the latest ones. It's not foolproof, but it doe…

Yeah, I was totally with the author for steps 1-7, but I have problems with the last four steps. Personally, I think step 9 shows exactly where the author is a bit out of touch. He seems to see GitHub as a sort of code social media site where statistics about the repository are just as valuable as the code itself. In some cases (especially open source), I can see that being kind of true, but I think GitHub gets far m…

I find the commit messages confusing, but find the last changed dates more useful (probably because of overly large mega-commits)

Re: Redesigning GitHub Repository Page

#163

First half of the article that redesigns the navigation is actually pretty good. It got me hooked and i find it valuable. When they started touching the content, I got a lot more hesitant. 1. I can't articulate why , but honestly it's extremely useful to see the last commit message on each file. It gives me a sense of which files have changed and if my changes are still the latest ones. It's not foolproof, but it doe…

> I can't articulate why, but honestly it's extremely useful to see the last commit message on each file.

Pride and curiosity.

If they are your changes, and they are on a big/famous project, it's immensely rewarding to stare at your name in the commit log. Making things a simple chronological list only emphasizes the most recent committers overall. The fact that you're a ninja who improved something that nobody else was willing to is obscured. It satisfies the human "mastery" motivator.

As for curiosity; I'm not going to pretend to be some compiler or JIT guru (although I wish I was). That being said, I can focus on that area of and see what people have been doing, possibly scraping off something off of that wisdom iceberg.

I have a huge amount of respect for the magical things that designers do in my company (the first video on this page[1] is a short demonstration of their utter and humbling talent). That being said, I've disclosed a pretty big idea to these guys and they're talking about ingesting bulk email into ML to learn user habits and suggest ideas. No, guys! Not only are you missing the point, but you're violating privacy!

We all do it. Developers come up with grandiose designs for shit that nobody needs. Designers come up with ideas that are technically impossible. Sales sell things that don't yet exist. Support will stop at nothing, including breaking everything, to solve one issue. Corp/management will create enough processes and red tape that nothing can get done.

I'd still take this article very seriously as Github. There's certainly things there that I wouldn't use but that design is clean and awesome.

[1]: https://www.k2.com/platform/workflow

Re: Redesigning GitHub Repository Page

#164

Half of this works well; some of the redesign of tabs, the elimination of icons, and similar changes look great. On the other hand, showing the last commit and change time for each file is useful . Where is that information now? It's in a linear commit list, which is helpful for different purposes ("when was the repo last updated and what's up?") but doesn't serve the original purposes as well ("when was this file up…

bingo.

Re: Redesigning GitHub Repository Page

#165
I'm supposed to trust someone about design when they have that horrid yellow background? /s

Jokes aside, I was skeptical but I think the (2nd to last) result is really good. I see a lot of the logic behind it and I could get used to it. There is a lot of good thought that GitHub could draw from there.

The final theme changes were trash though. Something both his blog and new design fail at is contrast. I use a darkreader plugin because I'm young and don't want my eyes to crumble to dust before I die. That blue-on-white is not going to fair well when inverted (or however dark readers work).

In some sense, I think that github might consider his UX advice, but should ignore his style advice.

Re: Redesigning GitHub Repository Page

#167

First rule of design: Know your user. Second rule of design: You (the designer) are not the user. I think the general criticisms here are because this designer didn't follow these 2 basic rules.

They have >500 commits on Github in the last year. I’m pretty sure that makes them a user: https://github.com/tonsky First rule of life: don’t stereotype people (“designers aren’t coders”). Second rule: check before leveling ad hominems.

For what it's worth, 500 commits is <2 commits per weekday for a year, which seems pretty low for the kind of power user I would assume github is actually designed towards.

Re: Redesigning GitHub Repository Page

#168
I really enjoy this kind of articles. The author started with small logical steps that indeed made sense and then he did a crazy leap to nowhere. The final outcome is silly.

In any case, I would like to see a follow up article, taking account of the feedback. That is how design works... iterations

Post reply on HN