Internetworkers: http://www.ibiblio.org/internetworkers/

[drua AT fullseven.com]

>"The next time you are asked to evaluate a piece of
> enterprise software, ask yourself one simple question:
> Was this software written in a way that increases my
> job security and gets me home at a reasonable hour, or
> was written in a way to enrich consultants at the
> expense of my organization?"

And then they can create some more "Tools HR can use", which ask employees:
When evaluating software, do you base your decisions on:
A) Whether the technology is crap based on well-honed
engineering expertise.
B) Whether the technology will contribute to your employer being more 
effective and valuable.
C) Whether or not it affects your job security and getting home on time.

If a software platform eliminates the need for 20% of the engineers in an IT 
shop, should they trash it to keep job security? If a 
pain-in-the-ass-to-implement system generates 10% greater returns long term 
for all of the profit share of our 5000 employees, should we do without it 
because a team of 20 in the IT department has to work overtime for four 
months to get it integrated?

And I had another question about that article's: If the engineers are worried 
about not getting home on time, I assume they are sorely needed at work. If 
that is the case, why the concern about job security? Simply rhetorical.

I know, I know, the article was just posing thought provoking questions. 
Ditto. :)



> Subject: Tools IT can use
> From: "Josep L. Guallar-Esteve" <jlguallar AT maduixa.net>
> Date: Tue, 4 Jun 2002 12:30:04 -0400
> X-Message-Number: 5
> 
> A nice article, about a new way of selecting applications:
> 
> http://www.infoworld.com/articles/op/xml/02/06/03/020603opnoise.xml
> 
> > 
> 
> 
> Salut,
> Josep
> -- 
> Josep L. Guallar-Esteve, QA-Test Engineer, Red Hat, Inc.
> http://www.ibiblio.org/sinner/
>