The Wetware Crisis: The Dead Sea Effect (2008)
brucefwebster.com
The Wetware Crisis: The Dead Sea Effect (2008)
1–10 of 55 posts
Re: The Wetware Crisis: The Dead Sea Effect (2008)
#2Really, that's all the article has to say. You're welcome.
Re: The Wetware Crisis: The Dead Sea Effect (2008)
#3"What's wrong?"
"Sam asked me what a traceroute was."
Sam was the longtime Novell admin. Yes this was a while ago...
"The worst part was, I patiently explained it to him, and he just asked me why that was useful?"
Just one example. There was more, of people of low competence who were very entrenched.
Re: The Wetware Crisis: The Dead Sea Effect (2008)
#4TL;DR: more talented people tend to move on to more lucrative gigs, leaving less talented people behind. The title draws an analogy to the Dead Sea, where water evaporates and leaves salt behind. Really, that's all the article has to say. You're welcome.
Re: The Wetware Crisis: The Dead Sea Effect (2008)
#5TL;DR: more talented people tend to move on to more lucrative gigs, leaving less talented people behind. The title draws an analogy to the Dead Sea, where water evaporates and leaves salt behind. Really, that's all the article has to say. You're welcome.
Re: The Wetware Crisis: The Dead Sea Effect (2008)
#6Re: The Wetware Crisis: The Dead Sea Effect (2008)
#7A single talented carpenter with an energetic but otherwise totally unskilled helper can accomplish more in a shift than two talented carpenters together. If you don't have someone to run to the truck for nails, hold shit, move ladders, etc. productivity suffers because your talent is wasting time on menial tasks.
Same thing applies to IT departments. The folks the author is busy sneering at are at least as valuable as the engineers they're actively trying to retain because (among other things) they soak menial tasks that would otherwise cut into their rockstar's productivity.
Re: The Wetware Crisis: The Dead Sea Effect (2008)
#8After college, I lived with a friend who worked in the IT department at our college. He got called in on a Sunday once, and came back around lunchtime quite flustered. "What's wrong?" "Sam asked me what a traceroute was." Sam was the longtime Novell admin. Yes this was a while ago... "The worst part was, I patiently explained it to him, and he just asked me why that was useful?" Just one example. There was more, of p…
Re: The Wetware Crisis: The Dead Sea Effect (2008)
#9It's thinkpieces like this that make me believe that IT professionals specifically and white collar workers generally would benefit greatly from a mandatory 24 month stint on a construction crew. One of the most important lessons any job foreman can learn is that every crew needs at least one lame duck. A single talented carpenter with an energetic but otherwise totally unskilled helper can accomplish more in a shift…
Re: The Wetware Crisis: The Dead Sea Effect (2008)
#10After college, I lived with a friend who worked in the IT department at our college. He got called in on a Sunday once, and came back around lunchtime quite flustered. "What's wrong?" "Sam asked me what a traceroute was." Sam was the longtime Novell admin. Yes this was a while ago... "The worst part was, I patiently explained it to him, and he just asked me why that was useful?" Just one example. There was more, of p…
Well, it was Novell. So not that entrenched after all.