9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: lucio@proxima.alt.za
To: 9fans@cse.psu.edu
Subject: Re: [9fans] asn.1 alternatives
Date: Sat, 11 Feb 2006 18:05:41 +0200	[thread overview]
Message-ID: <8218ff6a1a57a150abfee58726f26a5a@proxima.alt.za> (raw)
In-Reply-To: <541ac7952476f11c319d81a7b9f7d516@terzarima.net>

> also, in my experience, managers (pointy-head or not) are rarely overly
> caught up by the technical details.  they just want such-and-such a problem to go away.
> they usually don't really care how you do it, especially if it works well
> and they never ever have to cut short a trip to the golf course because of it.

I don't share your luck and I think few do, although this forum may be
more fortunate in that respect.  I am heading to Cape Town tomorrow
morning to install MS Exchange in what will probably still be a NetBSD
shop for a year or so.  Me, when I have no idea what Exchange actually
look like!

This is what comes of bucking the trend successfully.  IT management
there believe it will cost them less to entrust the installation to me
than to bring in an MCSE (by whatever the current label may be) that
will install herself permanently behind the Exchange keyboard at a
formidable monthly salary.  What will in fact happen, sadly, is that
I'll be blamed for all the things that will go wrong with MS Exchange,
irrespective of the real responsibility, more things will go wrong
than usual because I'll insist in front-ending Exchange with the
existing Sendmail installation, modified in haste to deliver to
Exchange instead of the local mailboxes.  All sorts of extremely fancy
features of Exchange will be used and the reliability of the existing
system will soon will be forgotten.

My shoulders aren't wide enough to carry that load, but I can't afford
to charge them what would be market related fees for my experience
because it is not what they and their colleagues perceive to be the
mainstream, so I'll have to sneak away from under their system very
slowly and very surreptitiously as soon as I can find an alternative
position.  They will not, of course, discuss this, as they do not want
to be encumbered with the necessary and unpleasant reality.

Sigh!

++L

PS: If you have a broad-spectrum position at Vitanuova that involves
vision rather than productivity, I'm your man :-)



  parent reply	other threads:[~2006-02-11 16:05 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-11  0:10 [9fans] More 'Sam I am' quanstro
2006-02-11  3:01 ` jmk
2006-02-11 14:29   ` [9fans] asn.1 alternatives Charles Forsyth
2006-02-11 14:54     ` Sape Mullender
2006-02-11 16:13       ` lucio
2006-02-11 16:57       ` Skip Tavakkolian
2006-02-11 16:05     ` lucio [this message]
2006-02-11 17:52       ` Marina Brown
2006-02-11 16:28     ` Dan Cross
2006-02-11 16:53       ` Charles Forsyth
2006-02-11 22:47       ` Brantley Coile
2006-02-20  0:04     ` Harri Haataja
2006-02-11  6:04 ` ASN.1 (Was: [9fans] More 'Sam I am') lucio
2006-02-11  6:54   ` geoff
2006-02-11  8:06     ` lucio
2006-02-11  8:44       ` geoff
2006-02-11 12:10         ` lucio
2006-02-11  8:55     ` Steve Simon
2006-02-11  9:16       ` Bruce Ellis
2006-02-11  7:04   ` Skip Tavakkolian
2006-02-11  7:09     ` geoff
2006-02-11  7:53       ` lucio
2006-02-11  7:53       ` Skip Tavakkolian
2006-02-11 16:37 [9fans] asn.1 alternatives quanstro

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8218ff6a1a57a150abfee58726f26a5a@proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).