4 ms·

To some extend, but there’s tasks that I could do in 30m in a company with 15 employees that I have still not accomplished after 2 months in our 15k employee en

by Aeolun 3y ago

To some extend, but there’s tasks that I could do in 30m in a company with 15 employees that I have still not accomplished after 2 months in our 15k employee enterprise.

wkat4242 3y ago
This so so much. Some tasks take me 10 minutes but it takes me half a day to jump through all the hoops that our colleagues have thrown up. Excel approval sheets, annoying proxies with SSL inspection (try configuring all that in multiple docker containers), having no access to actually configure what I need to do so I constantly have to put in tickets to other teams.. The worst thing is when they then outsource the work and ask us why they can do it so much faster.... :X
briHass 3y ago
Large orgs almost become like a bloated government in that way: groups start to construct little fiefdoms with rules and policies that are ostensibly constructed to improve quality. However, those rules end up becoming bludgeoning tools used by nefarious actors in those groups. The real problem is that nobody ever steps back and asks: are all these rules actually helping to improve quality of the software. Is the cost of the reduced velocity and overhead actually worth it in the end. Then, the org does layoffs and all that policy is still in place without the necessary people to supported the bloated workflow.
- rrr_oh_man 3y ago
  > are all these rules actually helping to improve quality of the software While I agree with your sentiment, high quality software (and: what is high quality, anyway?) is not necessary the goal of an enterprise.
  - Aeolun 3y ago
    Faster development almost invariably is though. Everyone wants to be able to say their project got done on-time and according to spec.
- pixl97 3y ago
  Even this isn't really looking at the problem correctly. If your two man organization if one person steals the source code or slips in some back door into the code, it should be somewhat obvious who did it. On the other hand in that large enterprise someone doing the same could lead to an international incident. And with that many people you are going to have nefarious actors at some point and you need to think about how to minimize their damage. It's likely you're falling into the same trap of understanding why Chestertons fence was put up in the first place.
  - briHass 3y ago
    The problem is, the whole mess becomes so abstracted away from the real goal: shipping software to customers and making money. Government can get away with it, because they're the only game in town, but a company doesn't have the luxury of operating with a crippling level of inefficiency for long. Whatever 'deal with the devil' that existed when the fence was erected may no longer be relevant or worth the overhead, but the policies live on. There may even now be individuals who's jobs are now directly related to enforcing/implementing the policy, and they have an interest in perpetuating it at any cost.
Veuxdo 3y ago
Linear scaling is more the exception than the rule, no? And it not just for "tech" either: it's unlikely you could learn the names of 15k employees in 2 months, for instance.

by Aeolun 3y ago

To some extend, but there’s tasks that I could do in 30m in a company with 15 employees that I have still not accomplished after 2 months in our 15k employee enterprise.

wkat4242 3y ago

This so so much. Some tasks take me 10 minutes but it takes me half a day to jump through all the hoops that our colleagues have thrown up. Excel approval sheets, annoying proxies with SSL inspection (try configuring all that in multiple docker containers), having no access to actually configure what I need to do so I constantly have to put in tickets to other teams.. The worst thing is when they then outsource the work and ask us why they can do it so much faster.... :X

briHass 3y ago

Large orgs almost become like a bloated government in that way: groups start to construct little fiefdoms with rules and policies that are ostensibly constructed to improve quality. However, those rules end up becoming bludgeoning tools used by nefarious actors in those groups. The real problem is that nobody ever steps back and asks: are all these rules actually helping to improve quality of the software. Is the cost of the reduced velocity and overhead actually worth it in the end. Then, the org does layoffs and all that policy is still in place without the necessary people to supported the bloated workflow.

rrr_oh_man 3y ago
> are all these rules actually helping to improve quality of the software While I agree with your sentiment, high quality software (and: what is high quality, anyway?) is not necessary the goal of an enterprise.
- Aeolun 3y ago
  Faster development almost invariably is though. Everyone wants to be able to say their project got done on-time and according to spec.
pixl97 3y ago
Even this isn't really looking at the problem correctly. If your two man organization if one person steals the source code or slips in some back door into the code, it should be somewhat obvious who did it. On the other hand in that large enterprise someone doing the same could lead to an international incident. And with that many people you are going to have nefarious actors at some point and you need to think about how to minimize their damage. It's likely you're falling into the same trap of understanding why Chestertons fence was put up in the first place.
- briHass 3y ago
  The problem is, the whole mess becomes so abstracted away from the real goal: shipping software to customers and making money. Government can get away with it, because they're the only game in town, but a company doesn't have the luxury of operating with a crippling level of inefficiency for long. Whatever 'deal with the devil' that existed when the fence was erected may no longer be relevant or worth the overhead, but the policies live on. There may even now be individuals who's jobs are now directly related to enforcing/implementing the policy, and they have an interest in perpetuating it at any cost.

Veuxdo 3y ago

Linear scaling is more the exception than the rule, no? And it not just for "tech" either: it's unlikely you could learn the names of 15k employees in 2 months, for instance.