Hier die für mich wirklich nicht mehr leicht schockierenden Auszüge aus dem Blog, auf das sich vowe bezog:
http://www.developingstorm.com/2005/04/my-hardest-interview-question.phpSure there were tricky technical issues I faced but they were nothing compared to the bureaucratic mess - goat rodeo - cluster fuck, that was Workplace 1.1 and 2.0. (2.5 is better and 1.0 was a lot of fun but they're both different stories).
he worst example of a procedural problem gone out of control was the Portal install. In Workplace 1.1 and much of 2.0 when you needed to install the latest build of Portal server it took anywhere from two days, if you were lucky, to a week or more of tedious hand editing of configuration files before the server would run. There was no automation for the process and no organizational investment in automating the process, so every few weeks all progress on Workplace would grind to a halt as people manually updated their servers.
Also nochmal: "[Portal Install] There was no automation for the process and no organizational investment in automating the process, so every few weeks all progress on Workplace would grind to halt as people manually updated their servers".
[Portal Install] There was no automation for the process and no organizational investment in automating the process
[Portal Install] There was no automation for the process and no organizational investment in automating the process
HEY. DAS IST FUCKING UNGLAUBLICH!!!
In comparison to the mind numbing procedural issues faced on Workplace, database deadlocks and thread safety errors paled as problems; days spent pouring over pages of logs looking for hints to a problem were a luxury and rewriting large chunks of someone else's code at the last minute to fix a critical issue was simple child's play.
Die Diskussion ging weiter. Ich mußte natürlich auch was sagen, stelle aber mich nicht auf die selbe Stufe zu Damien Katz, dessen Stimme (hoffentlich auch bei IBM) ein gewisses Gewicht in Sachen Glaubwürdigkeit hat:
Damien, I'm not sure having the creative people in control is the best business model to follow.
— Tony S Lee, 2005-04-22 22:19 (typical IBM a****** (englisches Wort mit 7 Buchstaben, beliebt auf Bile-Blog)
Tony you are right.
For business model you need to define target groups:
"stupid developer who needs java super-platform"
"stupid customer who needs loads of buzzword"
I have bad subjective feeling with workplace, too.
Will it scale, this xml stuff?
Personally I find more fun spring and jboss.
There is nearly zero echo to workplace in popular java sites like javablogs or javaranch.
Doesn't workplace need community?
Is anybody currently reading articles on notes.net?
I am used to that installation of IBM products has lots of gotchas (with some exceptions like wsad or, hey, lotus domino).
Actually, our backyard hardcore programmers told me that workplace express is easy to install. The non-express full product is different story. But appears as if you need to know a lot of stuff to get something deployed.
At the moment they like much more to code their own Eclipse RCP stuff instead of Workplace.
Thanks for posting this vowe. Sorry for posting so long, stupid text.
Axel
— Axel Janssen, 2005-04-22 23:47