2 ms·
I don't think what you're saying contradicts the article. Especially the example of the devops bottleneck -> hire a devops team. That's more or less explicitl
by kelnos 7y ago
I don't think what you're saying contradicts the article.
Especially the example of the devops bottleneck -> hire a devops team. That's more or less explicitly covered: "Prioritize the development of force multipliers".
The idea is that adding a new person to a team increases the work capacity of that team linearly to do the work that the team has been doing, in the same way they've been doing it. Finding new, more efficient ways to do the work is how you increase productivity, not work capacity. Hiring an Eli Whitney means that your work capacity is now devoted to doing something else (operating a gin rather than separating by hand), something that has higher productivity per time unit.
- wyattpeak 7y agoThis doesn't remove the contradiction, it only moves the contradiction into the article. It's not as though the article makes a soft claim which should be interpreted generously, it makes a very strong claim - "at most linearly" - despite the fact that there are all sorts of exceptions. That is certainly not "at most linearly", perhaps "at base case linearly".
- franciscop 7y agoThe author seems to conflate work capacity with work hours, which is what I'm trying to disprove. Work capacity is IMHO the maximum that a company can accomplish given the resources, which in a multi-skill team can be super-linear if a skill is lacking and it's supplied. The work can be the same but if made by a specialist it's more efficient in a non-linear way. I am sure someone was doing devops before but if an expert does it then it'll improve everyone's life by leaps and bounds.
- techslave 7y agothere isn’t a devops “team”. devops isn’t a job role, it’s a way of life.