Live data from Hacker News

I'm a serial over committer

swanson.github.com

21–30 of 49 posts

Re: I'm a serial over committer

#24

This is me right now exactly. I am swamped because i have over committed to too many thing. It is stressing me out and I don't know how to escape.

Are there any commitments that you can put on pause? Maybe you can't just drop the project, but if you aren't going to have time to work on it for a month, then officially delay it for a month so it's at least off your mind.

Re: I'm a serial over committer

#27
Well said. I completely empathized with your sentiment. So much so that I had to write more in response them what is probably appropriate in a comment section.

I commit to small one-off projects for friends, longer-term work with acquaintances, and whip up my own projects all the time. Sometimes the projects are freelance, and sometimes they are simply "free." All this serves to satiate the needling feeling in the back of my brain that I might just be missing out on something.

Here's the rest of my thoughts: http://blog.glenelkins.com/the-over-committers-dilemma/

Re: I'm a serial over committer

#28
Nothing undesirable happens immediately as a result - except that maybe your manager is a little bummed out. But maybe the next time one of these projects comes up, they’ll ask Bob first. Maybe that speculative project turns into a full fledged project and you missed your chance to work on it.

And when the over-committer Bob ducks out of the project due to time constraints, the manager will come back to you, knowing you have a good track record of completing tasks.

Re: I'm a serial over committer

#29

I thought this was going to be about someone meticulously doing git commits after every tiny little change.

I'd like to read a post about the optimal granularity of git commits in different situations. I don't think I'm experienced enough particularly when it comes to intense collaboration to write it myself

Re: I'm a serial over committer

#30

I thought this was going to be about someone meticulously doing git commits after every tiny little change.

I thought it was either that, or someone who carefully used fast-forward merges and rebasing to give the illusion of a completely serial history for a project that actually involved a fair amount of branching.
Post reply on HN