4 ms·
Sure for a small individual team or org. But getting this to scale isn't feasible. As companies grow they tend to hire based on specific skill sets. Thats when
by thegabez 7y ago
Sure for a small individual team or org. But getting this to scale isn't feasible. As companies grow they tend to hire based on specific skill sets. Thats when you start seeing the split into either dev or ops, which brings us back to the need for a small high performing with devops mentality...the devops team.
- _betty_ 7y agoWhy not hire "devops" skill into each team instead of creating a silo? Massive reason behind devops is to get Dev teams to take more ownership of ops so they improve their Dev practises, I don't see a dedicated team being able to improve the code base in the same way.
- thegabez 7y agoThere are many ways to implement "devops", this is one of them.
- dragonwriter 7y ago> Sure for a small individual team or org. But getting this to scale isn't feasible. Based on...what? > As companies grow they tend to hire based on specific skill sets By which you probably mean they tend to prefer hiring more narrowly specialized individuals. That may be a common trend, but to the extent it stops you from hiring or training for devops across your technical organization, it's incompatible with any meaningful devops implementation. DevOps doesn't work as a silo, any more than (as an enterprise I know pretends to do) can you do kaizen by way of an isolated “Kaizen team” reporting to a senior executive. Some things are definitionally not siloes and “doing” them in a silo is a failure to do (or even understand) them at all.
- z3ncyberpunk 7y agoMaybe not everything is about scaling it up?