6 ms·
Oh boy... That leads on to another thing that most non-technical (and even some technical!) managers don't understand: IT people are not drop-in modular compone
by chris_wot 11y ago
Oh boy... That leads on to another thing that most non-technical (and even some technical!) managers don't understand: IT people are not drop-in modular components that will instantly work!
Here's an example: I did some BI work in Qlikview. The existing reports for a particular division were badly written, and were each loaded manually for each client. Due to a number of reasons, we weren't able to change this situation immediately, but we kept what we had running even though it was incredibly inefficient.
Eventually it got to the stage where we needed to get the reports working in an automated fashion. I had a solution I was willing to work on, but was unable to find the time to do it as my primary responsibility was to another BI project.
The manager kept putting off getting new resources, and tried to "fix" the reports himself, only ending up breaking them completely.
The solution that management came up with was to employ a new resource. However, by the time they employed the new person they had 3 days to get the reports working. The problem was that even though the new person understood Qlikview exceptionally well, he didn't understand (and had no way of knowing immediately!):
1. What the dashboards needed to show (not documented)
2. The data sources used in the Qlikview dashboard
3. The way the Qlikview load script had been coded
As the guy was really, really good it ended up taking just under two weeks to get to grips with the underlying data structures and business requirements. The implementation to fix the numerous dashboards took another week. Then fixing any issues took another week and a half. So that was about a month and a half of work to get the guy up to speed, then implement a solution.
Management expects someone to be like a field replicable unit, that you can drop-in and replace on a project. But that is not the way these things work - the nature of people and projects (which are each different) is that there is ALWAYS a lead time - sometimes up to months depending in the complexity of the project - where the new person you employ (no matter how good they are) needs to familiarise and understand the systems and requirements of the business before they can actually do productive work.
- pnathan 11y agoOrthogonal nit, you tripped over one of my soapboxes: "employ a new resource". People are not resources, like a vein of coal. They are individual. Which was your point. But using the word "resource" instead of "person" perpetuates bad ideas.
- chris_wot 11y agoAgreed. My bad, in fact I acknowledge the irony, given my point (as you have picked up!) is you cannot treat contractors like a physical commodity! I appreciate you highlighting that discrepancy in my comment :-)
- arethuza 11y agoThat's one of my own wee foibles - I never refer to a person as a "resource".
- chris_wot 11y agoThat's less a foible and more a character strength :-) the foible is referring to someone as a mere "resource" (and yes, I am acknowledging my own foible here!).
- devonkim 11y agoWhen you deal primarily with people whose primary roles and careers have been driven entirely by Taylorist managerial principles (fundamentally, the belief that managers are the ones that know best and most efficient instruments to allocate workers and efforts instead of relying upon workers themselves) then you're somewhat forced to deal with the language of contracts where people are interchangeable with the term and it's a reality you have to just deal with if you do business with them. It's treating all your workers like you're playing Starcraft rather than trying to manage an elite Navy Seals team where each person is fully capable of independent actions and thoughts. Rather, most large companies are used to rather low quality labor and I might dare to say that some companies prefer their "go do something" labor as fairly narrow while their managers are showered with praise and glory constantly for the work of those they're managing. It's hard for a lot of people on here to imagine dealing with 100k+ other coworkers but at a point you oftentimes have to abstract away what makes people human to work in most large corporations. I'm not advocating that this is correct, but much like slavery and flat world theory, I hope this becomes outdated and struck out as both completely ineffective from a business standpoint as well as unconscionable.
- 11y ago
- gizi 11y ago> Management expects someone to be like a field replicable unit, that you can drop-in and replace on a project. Someone needs to explain to me why would this be a bad thing? They bleed lots of money and that allows the Darwinistic decimation process to kick in and ultimately wipe them out. A fool and his money are easily parted, and that is how it should be. You see, someone who is not capable of programming, should not be allowed to manage programmers, because that simply amounts to an insult. He cannot do what you can do. Therefore, he is an idiot. Nobody wants to take orders from an idiot. Every single business on the planet is now, one way or another, turning into a technology platform. This means that in the end, it is programmers who will own and control everything, and not that bunch of idiots.
- deleted 11y ago[deleted]
- s73v3r 11y agoIt's a bad thing because it doesn't work that way. Software engineers are skilled workers, not assembly line workers. And business Darwinism doesn't really work. Otherwise Comcast would have gone under years ago.
- serge2k 11y agoHigh barriers to entry would have to be a factor in business Darwinism, wouldn't they?
- anon4 11y agoThey bleed lots of money and that allows the Darwinistic decimation process to kick in and ultimately wipe them out. Better yet -- they bleed lots of money but don't die out, due to being hugely profitable, so they continue bleeding lots of money and we finally get the trickle-down economy Reagan promised us.
- crpatino 11y agoThis is not how life works. It is how you wish life would work. Humans are social animals. The power to cause (or prevent) change in organizations is political in nature. The power to affect operations through technology is at best instrumental to the power to decide what effect is to be implemented. By ignoring these facts, programmers forego the opportunity to be seen as valuable allies and turn themselves into exploitable resources. No amount of progress, or "platformization" is going to change that. Sure, getting high paying jobs with little accountability can be kind of cool, in the short term. But you need to think what happens next. If social Darwinism is true, idiot managers will die out and be replaced with more competent managers. It will take years, but at the end of day, they will wise up. And if so many of them see programmers as a threat they will cut our jobs. To a degree, this is what we are seeing now. The older generation of managers learned that programmers are unreliable, so they outsource not to save money, but to mitigate the risk of having to deal with programmers directly. The next generation is learning that the 3rd parties that isolate them from programmers are unreliable too. I expect the next generation will be very reluctanct to have in house development at all, and that they will limit themselves to existing products from reputable companies, if at all. Hard to tell what happens when that option is also shown to be not reliable.
- jmhobbs 11y agoOff topic, but possibly the best autocorrect change I've ever seen; > inept endive
- chris_wot 11y agoLol! Dammed iPad :-) typos now fixed
- marcosdumay 11y agoAnyway, I doubt any big industry in the world can integrate a new machine at an assembly line in 3 days. I don't get where this idea that developers can be easily replaced come from. No other profession is, and really, not even machines work this way.
- cbsmith 11y agoI don't think it came from anywhere. I think some people believe it is useful to project that it is true.
- sopooneo 11y agoEverything you say rings true to me. So, I sincerely wonder, why hasn't a drive for higher profits fixed this problem?