It is tempting to accept this kind of requests because we are under the impression that it would help the product manager or the sales. It make us feel that we are doing something good for someone; we are nice. Actually our job is to be reliable, far before being nice or friendly. Our job is to provide a product of an expected quality in a controlled cost, even if it means that we sometime have to refuse to help someone we wish we could. Just refuse nicely.

Par un collègue dev.
Ce qu'il dit est également valable pour le métier de sysadmin.

Encore un excellent article signé Sandra Henry-Stocker qui en a également écrit un autre relatant ses 30 années d'expérience en tant qu'admin sys (https://jeekajoo.eu/links/?-w_7AQ)

Je pense que le plus dur dans nos métiers, c'est la priorisation car on ne sait jamais trop combien de temps on va avoir besoin pour résoudre tel ou tel problème que l'on rencontre. Je note d'ailleurs cette "méthode" pragmatique pour décider d'une priorité suivant le degré d'impact:
"""
value # people affected time req'd = priority (highest # = highest priority)
3 2 2 = 12 problem #1
5 1 4 = 20 problem #2
"""
lien via http://www.f.0x2501.org/s/?D5CCmA

Sandra Henry-Stocker relate ses 30 années d'expérience en tant qu'admin sys et explique comment son métier a évolué.

Petit extrait choisi:
"""
The downside: Compared to many IT jobs, there's not much climbing up the corporate ladder for sysadmins. As a systems administrator, you'll seldom be in the spotlight. You can easily still be a "bottom rung" (nobody reporting to you) worker after 30 years in the field. It's also hard sometimes to get a sense of value. You generally get noticed least when everything is running smoothly. Unless you resolve Big Problems, most of the people you support won't think about you very often. Maybe not even on Sysadmin Day.

Systems administrators are rarely customer-facing unless you count as customers the staff that use the systems that you keep humming along. And, even then, the big changes that you make are likely done after hours when everyone else is off duty and having a relaxing weekend or enjoying happy hour at the local pub. Do your job really well and no one will remember you're there.

The upside: The work is seldom boring and there's always something new to learn -- something breaking, some new coming through the door. Even after 30+ years, the work is anything but monotonous. And the job pays reasonably well. There's also a lot of variability in what you do and what you specialize in. You might automate all of your tasks or manage a huge data center, but there will always be something that challenges you and problems that need your attention.

Some of the significant trade-offs involve the kind of organization you work for. I worked in one company with only three employees and two independent contractors and other organizations with staffs of tens of thousands. The benefit of the smaller staff positions was getting to touch nearly everything and being involved in almost every aspect of the work. The big ones offered more chance of moving around and changing my organizational role fairly dramatically.
"""

Article remarquable.

A lire! Intéressant et même glaçant.
Maintenant j'aimerais connaitre la suite de l'histoire.