Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

177 Days of GitHub

ryanseys.com

Post reply on HN
Print view View original

31–40 of 43 posts

Re: 177 Days of GitHub

#31

Post by marblar »

hk__2 wrote: post #6

I tried the same thing a few months ago (this lasted 58 days), but some days you just don’t want to work. A few notes: - it’s the time of the commit which is important, not the push. So you can contribute on your projects locally if you don’t have Internet access (e.g. on vacations), and then push at the end of the week. It’ll be the same as having pushed everyday during one week (this works with personal projects, b…

This isn't really in the spirit of what you're trying to do, but you can set the --date of the commit, or even amend the commit after the fact if you haven't pushed.

Re: 177 Days of GitHub

#32

Post by CWIZO »

hk__2 wrote: post #6

I tried the same thing a few months ago (this lasted 58 days), but some days you just don’t want to work. A few notes: - it’s the time of the commit which is important, not the push. So you can contribute on your projects locally if you don’t have Internet access (e.g. on vacations), and then push at the end of the week. It’ll be the same as having pushed everyday during one week (this works with personal projects, b…

As far as I know contributions to master (or default) and gh-pages count.

Re: 177 Days of GitHub

#33

Post by mufumbo »

uow! I haven't even ever seen this streak thing (too busy commiting all the time). Mine is pretty big and I'm ashamed to make it public hehehe

Anyway, you MUST make commit an habit. If you're into gamification, force yourself to do that and you won't regret.

Re: 177 Days of GitHub

#34

Post by zsiciarz »

BruceM wrote: post #12

I'm currently on day 252 of a streak: https://github.com/waywardmonkeys/ Most days are pretty easy. Being that I maintain a large project (Open Dylan), there is almost always a simple bug to fix, documentation to improve, typos to correct, bugs to file, pull requests to merge from others. It has been great for keeping things moving and making sure that every day, I make at least a little bit of progress. Every day, a…

Right behind you with 230 days: https://github.com/zsiciarz

The contribution graph is in my opinion really a great motivational tool. Seems to work better for me than projects like Julython, however I'm guilty of a few single-commit days fixing a typo or updating some dependency packages. Looking forward to 365!

Re: 177 Days of GitHub

#36

Post by rodw »

bowlofpetunias wrote: post #15

And yet somehow we're still surprised when clueless managers try to measure productivity in lines of code or quality in test coverage percentage...

I don't see the comparison.

TFA isn't about a productivity metric, it's about establishing a habit. Everyone from Jerry Seinfeld to Anne Lamott to Pablo Picasso extoll the virtue of making a habit of doing some work--even sometimes crappy or merely symbolic work--every day. ("Inspiration exists, but it has to find us working")

But that said, it's not as if doing something every day is totally uncorrelated to productivity. Sure, it's a proxy metric at most, but doing something is eventually a prerequisite to productivity.

But then again, maybe I'm a "clueless manager" type because I'd also argue that test-coverage isn't totally unrelated to quality. It's also a proxy metric and one that's relatively easy to game, but come on, is there anything in software development you find measurable?

Re: 177 Days of GitHub

#37

Post by kanzure »

marblar wrote: post #31
hk__2 wrote: post #6

I tried the same thing a few months ago (this lasted 58 days), but some days you just don’t want to work. A few notes: - it’s the time of the commit which is important, not the push. So you can contribute on your projects locally if you don’t have Internet access (e.g. on vacations), and then push at the end of the week. It’ll be the same as having pushed everyday during one week (this works with personal projects, b…

This isn't really in the spirit of what you're trying to do, but you can set the --date of the commit, or even amend the commit after the fact if you haven't pushed.

You want to set both GIT_COMMITTER_DATE and GIT_AUTHOR_DATE when you git commit.

Re: 177 Days of GitHub

#39

Post by BruceM »

sspiff wrote: post #20
BruceM wrote: post #12

I'm currently on day 252 of a streak: https://github.com/waywardmonkeys/ Most days are pretty easy. Being that I maintain a large project (Open Dylan), there is almost always a simple bug to fix, documentation to improve, typos to correct, bugs to file, pull requests to merge from others. It has been great for keeping things moving and making sure that every day, I make at least a little bit of progress. Every day, a…

Are you aiming for the "at least one commit per day", or did this happen naturally as you worked on Open Dylan?

I aim for it. Clearly before the streak started, I was much more intermittent with some days passing without visible progress. :)

Re: 177 Days of GitHub

#40

Post by [deleted] »

sspiff wrote: post #20
BruceM wrote: post #12

I'm currently on day 252 of a streak: https://github.com/waywardmonkeys/ Most days are pretty easy. Being that I maintain a large project (Open Dylan), there is almost always a simple bug to fix, documentation to improve, typos to correct, bugs to file, pull requests to merge from others. It has been great for keeping things moving and making sure that every day, I make at least a little bit of progress. Every day, a…

Are you aiming for the "at least one commit per day", or did this happen naturally as you worked on Open Dylan?

[deleted]
Post reply on HN