Live data from Hacker News

A Hacker’s Guide to Git

wildlyinaccurate.com

11–20 of 120 posts

Re: A Hacker’s Guide to Git

#11

Does anyone else find this to be quite hard to read? Just visually. Especially length of the lines and thinness of the font.

No. You mean it uses all (well nearly all) the width of the screen? I am pleased to see that for once rather than stuffing it into some narrow column, the width of which I would have complained about 10 years ago.

Re: A Hacker’s Guide to Git

#13
post #2

I'd recommend another guide. "Pro Git" by Scott Chacon is excellent and welcomes patches, source for the book and its translations are on GitHub http://www.git-scm.com/book

For what it's worth, Pro Git doesn't really need recommendation, it's the first Google hit for half of my git related queries...

Re: A Hacker’s Guide to Git

#14

Does anyone else find this to be quite hard to read? Just visually. Especially length of the lines and thinness of the font.

Yes, the site designer could (should) have used the CSS setting `max-width` for paragraphs (specifying `width` for paragraphs is, however, a big no-no in web design).

Re: A Hacker’s Guide to Git

#16

Does anyone else find this to be quite hard to read? Just visually. Especially length of the lines and thinness of the font.

Here's how to fix it: https://www.youtube.com/watch?v=tIeCs8xwEzo

Steps:

1. max-width: 40em on wrapper element

2. font-weight increase from 300 to 400

3. include @font-face rules for Open Sans 400

Re: A Hacker’s Guide to Git

#18
post #2

I'd recommend another guide. "Pro Git" by Scott Chacon is excellent and welcomes patches, source for the book and its translations are on GitHub http://www.git-scm.com/book

What is great about Pro Git is that it is approachable by someone new to git, but also eventually takes the reader through an explanation of the internals of git. Definitely a must-read!

Re: A Hacker’s Guide to Git

#19
post #2

I'd recommend another guide. "Pro Git" by Scott Chacon is excellent and welcomes patches, source for the book and its translations are on GitHub http://www.git-scm.com/book

I appreciate that git is powerful, but should we really need to read a book just to get the best from a source control system? It seems overly complex to me at times (any time I do anything outside of my usual workflow).

Version control only makes up a part of the whole development process, and plenty of coders out there manage without any at all.

Re: A Hacker’s Guide to Git

#20

Does anyone else find this to be quite hard to read? Just visually. Especially length of the lines and thinness of the font.

No. You mean it uses all (well nearly all) the width of the screen? I am pleased to see that for once rather than stuffing it into some narrow column, the width of which I would have complained about 10 years ago.

How big is your screen?
Post reply on HN