I'm following this debate almost like an outsider. I was born and raised under a communist regime, where "the population" was carefully managed. Everyone knew everyone else's address and date of birth, but people had a legal document to prove who they were. Sure, that document could be stolen or faked, but it was at least a starting point.
In my opinion, knowledge of a social security number or a few other details is not a substitute for proof of physical identity. Biometrics, anyone ?
a 4-GL like VB is good when all the groundwork has already been done, and focus must move towards the application. As a 3.5-level language, Java came at a moment when the basis had to be laid for a new environment: web, application servers (but not much more).
Perhaps this new environment has now matured. If so, then there is no more reason for messing around with lower-level details. When the tehcnical infrastructure is the same for a large number of applications, then it is really time for a 4 GL.
Ten years ago, I've caught the Powerbuilder wave. At that time, all client-server applications had identical architecture, so a high-level 4 GL was the best solution.
here in Sydney, Australia, I've seen the reaction to this trend. Large employers didn't like the idea of body-shops getting rich, so they've imposed their own terms on prefered suppliers. In 2001, we have signed a trilateral contract, where each of the three parties was aware how much the other two are paying or getting( the employer, the body shop and myself). The body shop took 20%, still outrageous, considering that it was pure commission, without any benefit to me.
Now I've found another contract elsewhere, but the same body shop happens to be the prefered supplier again. They still take only 20% officially, but they managed to pinch another 3% off my back on a few obscure taxes.
The change in terms is due to the "supply and demand" rule. Let's just hope the IT job market picks up, hopefully sooner than later.
It is true that busy people have less time to read Slash Dot. But, as an ageing A/P, I was worrying about my retirement prospects well before being left without a job. I know many other people have had the same concerns, but never voiced loudly while the pay checks were coming.
>> maintaining a motivation level that will allow you to keep up with emerging trends, but not so high that you burn out.
Well said. The IT people who survive the longest are the ones which are able to combine innovation with repetitive work.
I have seen 60-year old taxi drivers, shop owners, etc. I have yet to see a single 60-year old hands-on Analyst-Programmer or Developer. But I could still imagine a 60-year old DBA or other kind of administrator.
Slashdot Mirror
In my opinion, knowledge of a social security number or a few other details is not a substitute for proof of physical identity. Biometrics, anyone ?
Perhaps this new environment has now matured. If so, then there is no more reason for messing around with lower-level details. When the tehcnical infrastructure is the same for a large number of applications, then it is really time for a 4 GL.
Ten years ago, I've caught the Powerbuilder wave. At that time, all client-server applications had identical architecture, so a high-level 4 GL was the best solution.
Now I've found another contract elsewhere, but the same body shop happens to be the prefered supplier again. They still take only 20% officially, but they managed to pinch another 3% off my back on a few obscure taxes.
The change in terms is due to the "supply and demand" rule. Let's just hope the IT job market picks up, hopefully sooner than later.
It is true that busy people have less time to read Slash Dot. But, as an ageing A/P, I was worrying about my retirement prospects well before being left without a job. I know many other people have had the same concerns, but never voiced loudly while the pay checks were coming.
>> maintaining a motivation level that will allow you to keep up with emerging trends, but not so high that you burn out.
Well said. The IT people who survive the longest are the ones which are able to combine innovation with repetitive work.
I have seen 60-year old taxi drivers, shop owners, etc. I have yet to see a single 60-year old hands-on Analyst-Programmer or Developer. But I could still imagine a 60-year old DBA or other kind of administrator.