No post body was provided.
Untitled topic
1–10 of 55 posts
Re: undefined
#2The conclusion of the article is quite mundane:
Rather than seeing any dramatic increase in programming productivity, we saw developers taking care of their housekeeping.
As Kan, our CTO, explained to me this morning: “ Facebook going down made developers clean their backyard”.
Re: undefined
#3I really want to share this with my colleagues, because it's funny. But I really don't want anyone in management finding out that things like Haystack exist. What a shame.
Re: undefined
#4As headline grabbing as this is, a single event is not data. I'm sure there are other outliers in their data that they've not written a "X improves developer throughput by y%" articles about.
Plus, measuring developer productivity by pull requests merged is a very noisy way to measure "throughput"
Re: undefined
#5I really want to share this with my colleagues, because it's funny. But I really don't want anyone in management finding out that things like Haystack exist. What a shame.
Why do you want them not to find out about Haystack?
Re: undefined
#6Why does a blog entry require JavaScript to be enabled?
Re: undefined
#7Unless I am reading the article incorrectly, the developers worked mostly outside office hours.
So, in a way, developers who are cut out from their social connections will work free overtime?
Re: undefined
#8Unless I am reading the article incorrectly, the developers worked mostly outside office hours. So, in a way, developers who are cut out from their social connections will work free overtime?
> So, in a way, developers who are cut out from their social connections will work free overtime?
Don't tell companies!
Re: undefined
#9Unless I am reading the article incorrectly, the developers worked mostly outside office hours. So, in a way, developers who are cut out from their social connections will work free overtime?
[deleted]
Re: undefined
#10I really want to share this with my colleagues, because it's funny. But I really don't want anyone in management finding out that things like Haystack exist. What a shame.
Why do you want them not to find out about Haystack?
There is not a single signal that would not be better defined by just asking your devs.
Don't use commit history to measure any sort of performance if you have competent managers who can communicate with developers, and don't accept "devs are hard to talk to" as an excuse.