Network Administration Thermodynamics

March 12th, 2004 by Sean D. Conway in

A method for labelling users before you invest all your energy in them.
Your rating: None

In the human network, administrators struggle to understand those they serve (managers and users) and live at peace in their network. At times, it becomes necessary to expand administrators' universe of hardware and software to include the sciences of thermodynamics and chemistry to increase their powers of survival.

Network administrators have to hone their compression skills if they hope to live with the state of constant flux that exists in IT departments. Compression skills allow administrators to collect large amounts of information, compress it and extract what is required to solve a problem. Compression also enables the administrator to use other people's knowledge and experiences to solve problems they themselves have. Notice the common theme? Problem solving.

A valuable aid to compression is classifying. I have developed three categories using my limited knowledge of physics and chemistry to classify the many masters that administrators are required to serve. The three categories are endothermic users, exothermic users and toxic users.

Endothermic users are those whose energy content output exceeds the energy content of the reactant. An admin can invest a small amount of energy into an endothermic user--showing them how to install a print driver--and the resulting output is greater than the energy expended. In this case, the user installs the driver on all the other systems in the department that need it.

Exothermic users are those whose energy content output is less than the energy content of the reactant. An admin can invest a large amount of energy in an exothermic user--showing them how to install a print driver five different times--and the resulting output is less than the energy expended. In this case, the user calls and asks if the admin can install a print driver.

Toxic users are users whose energy content output is negative without the presence of a reactant. Toxic users or toxic help are users who efforts reduce or hinder any efforts you have made to produce results. For example, toxic users delete all the print drivers on a computer before installing the wrong print driver. Of course, this all is done before they call to ask you to install a print driver.

Most administrators have only one classification for users; one variation is PIBKAC--problem is between keyboard and chair. Unfortunately, this attitude can have a negative affect on system administration. The common reactant for solving problems is energy, and administrators have a finite amount energy to invest. If an administrator can classify a user using the suggested categories before investing his/her energy, then the administrator has an opportunity to decide how much energy he/she is willing to invest. I hypothesize the administrator would invest larger amounts of energy into the endothermic users and less in the exothermic users. The result is an increase in problem-solving energy. The recommendation to administrators for toxic users is to classify them as fast as possible, so you can isolate them from being involved in any reaction. The output from toxic uses is always a drain on energy. Your goal is to minimize the drain.

To practice putting users in these three categories, I created the following test, called Classifying Users in Thermodynamics (CUIT), pronounced "cute".

A user asks for your help to solve a problem and takes notes during your explanation. This user has the potential to be a:

  • a) toxic user

  • b) exothermic user

  • c) endothermic user

A user asks for help to solve a problem and then finishes typing an e-mail while you explain the solution. This user the potential to be a:

  • a) endothermic user

  • b) toxic user

  • c) exothermic user

A user asks for help, takes notes during your explanation and then doesn't follow the notes. He instead decides he knows a better way of doing it. This user has the potential to be a:

  • a) endothermic user

  • b) exothermic user

  • c) toxic user

Many administrators would admit their networks would be perfect if only they didn't have users. A network without users, however, would be a network without need for administrators. Hopefully, this small insight might give energy-depleted administrators a badly needed recharge.

Sean D. Conway is a former college instructor turned network system specialist for a regional telecommunications company in Canada.

__________________________


Special Magazine Offer -- Free Gift with Subscription
Receive a free digital copy of Linux Journal's System Administration Special Edition as well as instant online access to current and past issues. CLICK HERE for offer

Linux Journal: delivering readers the advice and inspiration they need to get the most out of their Linux systems since 1994.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Anonymous's picture

Re: Network Administration Thermodynamics

On April 17th, 2004 Anonymous says:

The article is a humourous philosophical musing of an Information Technology. The classifications are of the human condition and not the characters they are assigned. It may have true meaning when the reader realizes "users" can be a methaphor for "administrators". Hummm (as the critique wags a finger)..... not nice LinuxJournal taking shots at administrators. Are you looking at me or am I paranoid?

Anonymous's picture

Re: Network Administration Thermodynamics

On March 15th, 2004 Anonymous says:

The author may be very knowledgable about systems administration but he does not appear to know anything about chemistry. He got "exothermic" and "endothermic" exactly the wrong way around.

Anonymous's picture

Re: Network Administration Thermodynamics

On March 29th, 2004 Anonymous says:

I woul have to agree, in a less configurable environment these would not apply, however working as a linux sysadmin for the government with a network of over 3,000 users, I get calls and have to figure out what the heck they are trying to tell me over the phone, this would be a good way to classify people

endothermic -- those people who call and say, " My computer is broken." Then proceede to clarify with, "I can't open the internet." The kind of people you keep having to add more and more energy to yet they keep absorping it, not giving off any clue of what is wrong

exothermic --- "My computer is froozen and I was editing my forecast and I didn't save it and I worked on it for 3 hours and I need this forecast so do whatever you have to do but do not lose that forecast because I worked on it for 3 hours and did not save it and I...." those who call in a panic, and want a pancea

toxic --- "What the f**k this stuff sucks, why can't we just have stuck with friggin HP machines, this ls crap, what is that, this is so shi**y, I hate the dam* stuff, come the fu** on now..."

Anonymous's picture

Re: Network Administration Thermodynamics

On March 15th, 2004 Anonymous says:

You're correct.

Exothermic reactions give off more heat than originally put in -- a huge forest fire started by a tiny spark is an excellent example of this. Endothermic reactions take in more heat than they give off. (BTW, exothermic reactions do not violate the second law of thermodynamics, since the energy given off is already contained in the reactant and the oxygen in the air, in the case of the forest fire example.)

In the Greek language, "Ex" means "Out" and "En" means "In".

Anonymous's picture

Re: Network Administration Thermodynamics

On March 25th, 2004 Anonymous says:

Agreed, but in biology, endothermic animals are warm-blooded, and maintain their body temperature (produce heat) when the environment is colder.

Exothermic animals are cold-blooded, relying on heat (energy) from the environment to give them energy.

If you look at it from the biological perspective, the author makes sense.

Anonymous's picture

Re: Network Administration Thermodynamics

On March 13th, 2004 Anonymous says:

Here's my take on this article.. It's an over explanation of simple human psyche.... You productive users/semi-productive users/those skimming by.. and the toxic users.. Which I do agree... They don't care... As long as the place of employment continues to give them a paycheck they'll still be miserable... Easy fix though... Only give admin access to those hired to admin the network.... If delegation is need.. Then get those that are to be delegated certified and trained in proper admin skills... At least A and Net+

Anonymous's picture

Network Administration Thermodynamics and Users

On March 13th, 2004 Anonymous says:

I work in a company with more than 2.000 users, and believe me, there are all kinds of them, ranging from the engineers who do it themselves, strip out the machine, rewire it and then work, to the average person who calls in desperately because has lost it

Anonymous's picture

Re: Network Administration Thermodynamics

On March 12th, 2004 Anonymous says:

Interestingly, I would say that for all the sample user behaviours you described, an 'all of the above' option is needed.

Users who take notes are often those you have to waste a lot of time on. Many are taking notes because they don't /understand/ the concepts involved, and aren't trying to learn them - they're noting down a procedure that's specific to the task. Often it's not even generalised to the point of 'connect to the desired server' instead of 'connect to MyDepartmentFileServer'. I have chronic note takers at work who are completely thrown by a change of desktop background. If they're nodding, possibly asking useful questions, and not saying "sorry, I haven't finished writing that bit down yet" all the time, you're more likely to be in luck.

Also, the user who will go around the rest of the dep't frequently qualifies as 'toxic' not helpful - they'll change things without fully understanding the consequences, and leave you a large mess to clean up. "You know that driver was the win9x version right? It does _bad_ things to WinXP machines... like the bunch you just installed it on." These users are also usually those who love "reorganising," and "cleaning up," (read: moving things around into structures that only make sense to them, or just deleting anything they don't understand).

As for the person who decides they know a better way to do it ... they might be right. Sysadmins have to be such jacks-of-all-trades that sometimes the user /will/ know a better way. I work in a newspaper, so I have to run SCO OpenServer, MacOS 9, Win9x and Linux on a LAN, with apps including QuarkXPress, Adobe InDesign, Acrobat, Photoshop, Illustrator, and at least 3 different custom or semi-custom packages. This is a lot to keep track of. Sometimes one of the Qui^Hark users will just have a better way to solve a problem that I do ; it's important not to discount that possiblity.

I don't think it's useful to try to categorise users. It is definitely useful to learn the way your users work and learn about them, but deciding on a fixed set of categories to drop them in seems unhelpful. I have users who you'd call 'toxic' (read: I spent an entire weekend locking down the ACLs on anything they could access and learning how to lock down their PC, as they're an enthusiastic "cleaner") who have taught me a lot about how to manage particular apps. I also have note-takers who can't even get past seeing the computer screen as a something where you click on particular pictures in particular orders to make it do things. I also have users who don't even understand maximising a window, but can show me a thing or two about Photoshop.

So ... basically, it's not that simple. I actually use one of my more generally clueless users as in-house Quark tech support, as they know /every/ little trick used to make the bloody thing behave if it's playing up. Yet you'll see them trying to 'get picture' to import a word document into a Quark graphics frame "because the customer said it had their logo in it".

Craig Ringer

Anonymous's picture

Re: Network Administration Thermodynamics

On March 12th, 2004 Anonymous says:

You left out the user who can teach the sys admin a thing or two. Keep your ego in check and don't be afraid to learn yourself. Perhaps it's because I'm a developer and dig much more deeply into dev issues than the sys admin. I have a different agenda than users. I am not interested in jumping through hoops to get a test bed for software I'm interested in.

One more tidbit--you left out the babalishous user. Any sys admin worth his salt (sorry ladies, but it's at least one order of magnitude more dudes than chicks in the sys admin world) should drop whatever he's doing (network upgrade, later) when he gets the call from DA BABE. I had one at me last gig downtown Seattle. She used to wear these tight ski pants/sweater outfit every once in a while. Yowza, did I ever like helping her set up a printer driver!

Anonymous's picture

Re: Network Administration Thermodynamics

On March 12th, 2004 Anonymous says:

> I am not interested in jumping through hoops to get a test bed for
> software I'm interested in.

The sysadmin also isn't interested in getting fired when the company gets rooted due to an unpatched exploit that got through because you wanted your test box "yesterday". :)
My point isn't that you're wrong, just that you're not the only one who's right. On a related note, the biggest problem I ever ran into with acknowledging an advanced user's skills (on issues with broad, visible effects) was that the other users would notice, and then it would inevitably be the bonehead who would start complaining that "you listen to his ideas, but never mine..." As nice as it would be to just flat out say "that's because he actually knows what he's talking about", you rarely can get away with that. :)

> Yowza, did I ever like helping her set up a printer driver!

Hey, I'd forgotten some of the reasons there aren't more women in the tech fields; thanks for reminding me of one. :p

Anonymous's picture

Re: Network Administration Thermodynamics

On March 12th, 2004 Anonymous says:

in my opinion it can be very harmful to give a user rights to install software, especially in windows, because if the user can install software he is at 99% Admin, which means that IE, worms, mail worms, viruses can spread very fast. Furthermore if you have a huge network you loose control of installed software, eg loose control of licenses.

Yes users that are smart and learn are good, but I limit this to applications and to give me detailed or helpful descriptions of their problem, because mails like "my internet is not working" doesn't help me at all.

I even disallow the user to change his password, because then they change to super simple things.

lg, clemens

(thought I "only" administrate 55 acounts, but you always have to plean ahead)

Post new comment

Please note that comments may not appear immediately, so there is no need to repost your comment.
The content of this field is kept private and will not be shown publicly.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <pre> <ul> <ol> <li> <dl> <dt> <dd> <i> <b>
  • Lines and paragraphs break automatically.

More information about formatting options

Newsletter

Each week Linux Journal editors will tell you what's hot in the world of Linux. You will receive late breaking news, technical tips and tricks, and links to in-depth stories featured on www.linuxjournal.com.
Sign up for our Email Newsletter

Tech Tip Videos

From the Magazine

December 2009, #188

If last month's Infrastrucuture issue was too "big" for you then try on this month's Embedded issue. Find out how to use Player for programming mobile robots, build a humidity controller for your root cellar, find out how to reduce the boot time of your embedded system, and if you're new to embedded systems find out the basics that go into one. You can also read about the Beagle Board, the Mesh Potato and a spate of other interestingly named items. And along with our regular columns don't miss our new monthly column: Economy Size Geek.


Read this issue