News: 1667976854

  ARM Give a man a fire and he's warm for a day, but set fire to him and he's warm for the rest of his life (Terry Pratchett, Jingo)

Boffins find COVID changed the way sysadmins work – probably for the worse

(2022/11/09)


Researchers from Germany's Max-Planck-Institut für Informatik have studied how the COVID-19 pandemic impacted the way systems administrators work, and found the profession was negatively impacted.

Their findings are detailed in a [1]paper titled "'I needed to solve their overwhelmness': How system administration work was affected by COVID-19".

The researchers spoke to 24 sysadmins hailing from 12 economies (eight European, two North American, plus India and Ghana) about "their day-to-day sysadmin work before, during, and after the lockdown was enforced to better understand how their work was impacted by the lockdown and the ways in which they managed this."

[2]

The researchers found that sysadmins face unique pressures in a crisis because it's their job to keep everyone else working – even as they have to adjust their own practices.

[3]

[4]

"The ability of sysadmins to adapt to a crisis then has a cascading effect on other workers' ability to adapt."

The study found sysadmins mostly just did whatever it took in the early days of lockdowns, before their organizations moved "from implicit to explicit coordination, and from informal to formal interactions."

[5]

That was a good thing in some ways – one of the interviewees said that lax security practices like password sharing didn't survive the early days of the pandemic. Others said remote work meant the pressure to do things because someone was waiting for them to happen was not felt when they worked from home.

"We see a connection between the lockdown forcing a formalization of coordination activity and a decline in perceived micro-management; spontaneous and chance interactions are replaced by asynchronous communications and planned meetings," the researchers write.

[6]Reg readers tell us what they wanted for SysAdmin Appreciation Day

[7]Remember that day in 2020 when you were asked to get the business working from home – by tomorrow?

[8]Some stayed in Croatian castles. Some hid in cars. We speak to techies who experienced lockdown in very different ways

[9]'It takes a hell of a mental toll' – techies who lost work due to COVID share their stories

While sysadmins appreciated the fact they were just left alone to work through lists of required activities, some found the need to prove they'd done their required tasks was more onerous than just talking to colleagues to let them know a job had been done.

The researchers argued that loss of spontaneous integration was not good for sysadmins or their employers, because organizations have come to expect that their techies are available to help, and sysadmins see it as a part of the role.

"The informal aspects which were integral to sysadmin work (spontaneous conversations, helping each other etc.) have been replaced by formal communication or were otherwise replaced with ill-fitting approaches," the paper states.

[10]

The researchers make three recommendations:

Minimize formal work styles that just make extra work for sysadmins;

Adopt tools that let sysadmins do what they do best while reducing the need for formal coordination of remote work;

Ensure that system administrators have sufficient authority over their work and responsibilities to shape and implement working processes that aid them in accomplishing their tasks.

The Register spends a lot of time pondering the lot of a sysadmin. In your correspondent's opinion this paper has useful insights into the profession and may open your eyes to how sysadmins are regarded inside organizations, and how the world of work works. It’s worth a read. ®

Get our [11]Tech Resources



[1] https://pure.mpg.de/pubman/faces/ViewItemOverviewPage.jsp?itemId=item_3384326

[2] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2Y2uIYfUq6tsyCqGTWIX6FQAAABM&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0

[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44Y2uIYfUq6tsyCqGTWIX6FQAAABM&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33Y2uIYfUq6tsyCqGTWIX6FQAAABM&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[5] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44Y2uIYfUq6tsyCqGTWIX6FQAAABM&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[6] https://www.theregister.com/2022/07/29/sysadmin_appreciation_day/

[7] https://www.theregister.com/2021/03/08/covid_logfile_wfh_part_one/

[8] https://www.theregister.com/2021/05/05/covid_logfile_extreme_wfh_part_two/

[9] https://www.theregister.com/2021/09/07/covid_logfile_part_iii/

[10] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33Y2uIYfUq6tsyCqGTWIX6FQAAABM&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[11] https://whitepapers.theregister.com/



Potemkine!

I'm not sure that 24 samples are statically significant, however the recommendations are common sense.

== Bring us Dabbsy back! ==

The old dilemma

Roger Kynaston

The trouble with any system (or desktop for that matter) support is that you are only noticed when things go wrong. I know that this is utterly unoriginal but it is still true. Back in the day, they noticed if the punch cards were not sorted properly. Now they notice if the auto-scale doesn't scale. Personally, I was too late to the party to experience punch cards and my current gig is not ready to step into the cloudy utopia. Plus ca change!

I am not sure what the solution is though I am already counting down to retirement.

I like lists!

chivo243

But not meetings so much, unless they were with my immediate team, those were productive.

Making changes

ColinPa

Someone said that as they moved towards the devops approach (during covid) , they changed the way they worked. For example if you wanted a new column to your table, you used to have to walkk roun, to, and put in a request to the DB2 admins.

Now developers have the authority to do it themselves, when they have got it right, then they raise a request for the db2 admins to progress it into the pre-production system. This had benefits that development/test could make as many mistakes as they wanted (whoops wrong data type, or that "new index didnt help") and Db2 admins had less work to do, and there was less time pressure( we want it now!).

One person in each development team was "trained" on the DB2 work and had the authority to make changes.

Of course after the first few times when development destroyed the database, they learned to be more careful.

More than sysadmins

Anonymous Coward

This - spontaneous conversations, helping each other etc.- so much was lost from my workplace when we al flew the coop.

In my org. (YMMV) virtual has never allowed for the same fluidity of just jamming with a whiteboard and a few markers to work through a complex problem/bounce ideas around.

Sure he's sharp as a razor ... he's a two-dimensional pinhead!