3 ms·

I've worked in technical jobs for non-technical managers - you don't need to understand the technology to be able to manage people working on it. To wit - why

by Aloha 9y ago

I've worked in technical jobs for non-technical managers - you don't need to understand the technology to be able to manage people working on it. To wit - why would they care about most of that - or for example, version control - why would they even try to argue against version control - version control is a free problem at this point, as in it doesn't cost money to fix - and it wouldn't even rise up to a non-technical managers level.

lordCarbonFiber 9y ago
People don't like things they don't understand. It's funny you chose version control as your example; I work at a company currently trying to modernize and getting version control is like pulling teeth. Without technical leadership from upper management you each individual line of business standing up their own infrastructure (there's currently a war between github and gitlab for the new step forward; the resolution of which is blocking the purchase of any additional github licenses). Perhaps a domain expertise isn't strictly necessary but it helps a lot; especially in older environments trying to change.
- CyberDildonics 9y ago
  > I work at a company currently trying to modernize and getting version control is like pulling teeth. If a company can't even understand the massive benefits with practically zero downsides of version control, they sounds like a company that is probably thoroughly screwed up.
nunez 9y ago
> version control is a free problem at this point, as in it doesn't cost money to fix - and it wouldn't even rise up to a non-technical managers level. You need to have just enough knowledge of version control to make that argument. And that’s the problem.
- Aloha 9y ago
  you start out using git, then can migrate to a better product once money comes - and the money comes - the stated complaint wasn't "doing version control right" it was "using version control" which to me means, no version control or version controlled.

by Aloha 9y ago

lordCarbonFiber 9y ago

People don't like things they don't understand. It's funny you chose version control as your example; I work at a company currently trying to modernize and getting version control is like pulling teeth. Without technical leadership from upper management you each individual line of business standing up their own infrastructure (there's currently a war between github and gitlab for the new step forward; the resolution of which is blocking the purchase of any additional github licenses). Perhaps a domain expertise isn't strictly necessary but it helps a lot; especially in older environments trying to change.

CyberDildonics 9y ago
> I work at a company currently trying to modernize and getting version control is like pulling teeth. If a company can't even understand the massive benefits with practically zero downsides of version control, they sounds like a company that is probably thoroughly screwed up.

nunez 9y ago

> version control is a free problem at this point, as in it doesn't cost money to fix - and it wouldn't even rise up to a non-technical managers level. You need to have just enough knowledge of version control to make that argument. And that’s the problem.

Aloha 9y ago
you start out using git, then can migrate to a better product once money comes - and the money comes - the stated complaint wasn't "doing version control right" it was "using version control" which to me means, no version control or version controlled.