4 ms·
It's largely identical in enterprise programming. I have a lovely and smart boss but I can not get him to look at stuff properly until after I roll out a poten
by noir_lord 8y ago
It's largely identical in enterprise programming.
I have a lovely and smart boss but I can not get him to look at stuff properly until after I roll out a potentially massive change to our internal ERP.
Real money on the line as well.
I think a lot of it is that non-programming managers don't really grok on the intrinsic level the vast complexity that can be under the skin of a seemingly simple change.
In fact that is largely our job I guess, to hide all that complexity, when a user selects "order following required stock from supplier" they don't need to know what is happening under neath, they just care about price and when it'll be delivered on a container to one of our sites.
- wozer 8y agoSomehow this even happens with programming managers. I feel like we have a real crisis of leadership in software development.
- torqueTorrent 8y agoI'd buy that for a dollar!
- leowoo91 8y agoThat's mostly because managers underrate the concept of 'optimization' and how features are interconnected. Once a developer makes a mistake, all other things already working, gets broken. Small changes are not so small after all. They need to be understood as a whole, instead of individual updates.