|
|
|
|
|
by PedroBatista
29 days ago
|
|
It can be. Because most automations never capture the complete scope of the job/task ( not even close ). Just like neurons, if you don't use it you lose it and when the inevitable problems come, nobody knows the why, the how and the what. At that point someone smart would incorporate all those real costs and opportunity loses on the "automating everything" equation. But they usually don't. Of course automating tasks is a must, but it's very far from being a black and white situation. These dynamics have been happening for centuries by now, nothing new. |
|
Management likes to think otherwise for a variety of reasons and peons such as myself know it is rarely that simple. Case in point, our team uses Jira, but Jira is not great at.. capturing efforts that are umm.. less code oriented. In fact, there are times when it is genuinely better to leave some details out for considerations that may simply not be part of coding considerations.
In other words, automation assumes proper capture of the entirety of the task, but, I have seldom seen it capturing anything but simple workflows well.