I guess I'm just ranting cause the project I've been working on has sort of been canceled. It's been a great project and interesting. But i've been on the low down ever since I got here as a contractor because they just don't like to hire IT people. So bring me in as a non-IT person, get the job done and no complaints. Problem was they didn't know how complex the system was or what it would take to get done. I improved the system and had to train mainframe programmers and blue collar clients, but there was still a lot of work to be done.
But as time goes on, management can't always be left in the dark. So while the manager I've been working for did a great job and was a great person, the upper level management started to peek around and wonder why other groups are using .Net and this project is in Java. So after a few meetings I never knew about, today I come in and bingo, they are going to go from java to .Net because the management thinks java and j2ee is too complex and they have a few people who have at least played around with .Net within the group and it's not going to be the groups "standard".
It wouldn't be a problem if i were a FTE employee. I'd just have to learn .Net. But since I'm a java/j2ee contractor and the project is now going in a different direction, I'm no longer needed. Kind of sucks. I liked the environment and the people.
Oh well. Now i have to find a new opportunity ASAP.
I have recently come to the conclusion that there's a "Law of Conservation of Programming Work". By which I mean that the overall amount of work required to create an enterprise-quality project is constant, regardless of the language used.
By way of illustration, when I first adopted object-oriented programming, I noticed that my projects debugged faster - once they compiled at all, they were usually pretty clean - but required more front-end design work. More recently, I've been working using scripting languages. I can get a site up and running fairly quickly, but, since the variables are all bound dynamically, things blow up randomly at run-time due to subtle data type mismatches.
Now personally, I'd rather have my embarrasments all up front in secret rather than repeatedly be called in the cold dark hours of the morning. But most people haven't got my perspective. They see a project getting into shape rapidly, so the hacked approach where little advance planning is required is wonderful. Besides, nobody really expects security or reliability from Windows apps, anyway.
And, now that I think of it, the fad of frittering away three-fourths of the alloted project time drawing stick figures hasn't done much for the credibility of rigorous project design. I believe in use-cases, but no design tool should ever be used to micro-manage the process down to the code level. Unless it's generating production-quality code itself and doing so as fast or faster than the coders would.
Blitzlügen - Lies or information broadcast, but when called out the broadcaster does little or nothing is done to correct them, thus allowing those who wish to believe to accept them as truth.
Lügensturm - A barrage of Blitzlügen fired in such quick succession that it is essentially impossible to correct them all.
Every snowflake is perfect and unique. And every snowflake contains a very tiny ad.