I can believe it.
What I've seen, is management doesn't consider that the jobs, the computer jobs,
the reports and output, run by themselves. They see the output and they see the employee
and they just figure that the employee has to do something to make the jobs run. Which is
a slightly different take on the article. They just get it in their heads that it is that
way and never really ask too many questions and everybody is happy. This can go on for
years or decades.
They also have a hidden fear that if the employee leaves, the jobs may stop and no one
will be able to "fix" it. They certainly can't. It's perhaps the only
job in their perview that they can't do. It's just magic and they don't want
to break the spell.
I myself experienced this. I had a repetitive data translation task to move data between
two systems. So I wrote a script to do it. I had expressly asked for permission to do
this, but was denied. I did it anyway, lets say, on my own time. I used the breathing
room to do other things, since I was busy and enjoyed my work and improving my skills.
It's a big reason why there was, as continues to be, push back from managment about
working from home. Many managers have no way to judge output. But they can judge input.
In software, the unit of measure may be keystrokes, but it almost always can be seat
time.
Over my career, good managers are rare. They can judge output and can delegate
effectively. Part of my later difficulty was that I had a lot of these managers, the good
ones, early in my career. When I had the bad ones, later on, I didn't understand them
and they didn't understand me. Whose gonna win that battle LOL.
I don't see AI being able to help with this.
On Wed, Nov 27, 2024 at 11:58:51AM -0800, Brian E. Lavender wrote:
Seen on Slashdot and posted Xitter.
Stanford Research Reveals 9.5% of Software Engineers 'Do Virtually Nothing'
https://developers.slashdot.org/story/24/11/26/1346219/stanford-research-re…
Seems like an interesting study.
Brian
--
Brian Lavender
https://www.brie.com/brian/
"There are two ways of constructing a software design. One way is to
make it so simple that there are obviously no deficiencies. And the other
way is to make it so complicated that there are no obvious deficiencies."
Professor C. A. R. Hoare
The 1980 Turing award lecture
_______________________________________________
Lug-nuts mailing list -- lug-nuts(a)bigbrie.com
To unsubscribe send an email to lug-nuts-leave(a)bigbrie.com