Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I think you're right about the mental modelling that leads to these market outcomes.

I am perplexed by the weak arguments from sources -- comparing dev work to 9 mothers trying to have a baby in one month? What point are they trying to even make there? My crystal ball is cloudy but I think they mean delivery time is immutable? The other, saying productivity differences encourage lack of communication? That's not even relevant to the exploration of the fact of how much productivity difference there is!

The whole question is somewhat beside the point: I don't understand the benefit of homogeneity. I don't have amazing productive work every minute of the day, heck, I don't have good productive work every week of the year. Making a system that homogenizes output would limit _all_ employees, because we all have times we are 100x better than us at our worst.

And yet, in order to get predictability, we strive to build systems where engineers are cogs, because if things are predictable, targets are met, and managers get their bonuses. But it ultimately doesn't serve the best interests of the business.



Homogeneity in developers is useful in the same way that homogeneity in servers is; it reduces the dimensionality of the problem. Instead of having 1 unit of 20 different resources to allocate, you have 20 units of 1 resource.

That said, sometimes (read: 10-100x developers) you sometimes have only 1 unit of 1 resource. And if you don't pay for it, you wind up with 0 units.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: