O.T.American programmers at Indian Wages ?

Top Page
Attachments:
Message as email
+ (text/plain)
Delete this message
Reply to this message
Author: der.hans
Date:  
Subject: O.T.American programmers at Indian Wages ?
Am 10. Dec, 2003 schw=E4tzte Derek Neighbors so:

> I think most IT people want their cake and eat it too. In high times the=

y
> "demanded" high salaries. Now in lean times they refuse to work for less=

=2E

I'll be less likely to bitch about working for less when firms guarantee
severance packages for low rung employees and stop dishing out $20 million
severance packages for executives.

Oh, and salesdroids can't make oodles more than I do or get free trips to
places because they, "oh my gosh", were just doing their job.

> I stumbled upon an interesting article that I rather liked. About role


It was on /. the other day.

> fragmentation within the IT sector and how it ballooned to a large degree
> earning and status roles and probably set us back 10 years.
>
> http://www.softwarereality.com/lifecycle/role_fragmentation.jsp


There are some decent points in here, but he's generally describing a borke=
n
system and I bet the developers in that system are just as borken as what
he's describing.

DBAs are necessary for Oracle. Maybe not for MySQL or PostgreSQL for
small projects. DBAs, as well as other employees, should be able to do thei=
r
job. I actually think DBAs should be sys_adms who specialize in the db. The=
y
definitely need to know how to write scripts for whatever platform the db i=
s
running on.

There are two roles that should be able to dictate terms to the devel team.
One is the security role, the other is the configuration/production role.

Most of the developers I've worked with don't even undertake the simplist o=
f
security measures. It's really sad. If it needs to be secure and it isn't,
it should be rejected.

I've worked with lots of software created by developers who have a love
for hard-coding configuration information. There's this really cool
concept called 'configuration files'. There's another one called 'command
line options'. Neither is very difficult to handle. BTW, it is mostly
proprietary "choice is bad" software that has this problem, but internal
projects also suffer greatly from it.

See my getopts.sh and getopts.pl templates. I'm not a great coder, but it
didn't take me long to create the two of these. If I programmed in other
languages very often, I'd write something similar for them.

https://www.LuftHans.com/unix/

If the developer doesn't want to deal with security concerns or deal with
having stable rollouts to production he/she should go bother someone else.

Mistakes happen. I can understand that. It's the lack of concern that
bothers me.

ciao,

der.hans
--=20
#  https://www.LuftHans.com/    http://www.AZOTO.org/
#  C'est la Net - der.hans