I work in an organisation where we seem to use PRINCE2 in name only. Once a project is under way the idea of PRINCE2 seems to be to only be concerned about bad things - ie. documentation revolves around things like risk logs and issue logs.
The trouble with where I work is that we bury our heads in the sand when something is wrong. I think this stems from management being scared that if anything bad is documented then it might be used against them. I can kind of see how this might not be so uncommon but would be interested in how this works in a proper environment.
Hehe, having seen some truely awful code where I work (in Java too!) I've always been amazed that our apps run quickly let alone at all.
I think unless you are writing some intensive processing loop go for the neat code.
From another point of view though I've always found clever optimisations very interesting (eg. pixel plotting).
Don't think that by having the word 'enterprise' in the product means there is anything special about it. I've got a bunch of servers with ES pre-installed and it's scary to know that in my 'enterprise' environment I have xeyes and kdegames installed. I could mention _so_ many more....
Basically all RH-ES does (IMHO) is allow companies with FUD-infected management and cowboy SAs to feel happy that they have 'enterprise' Linux systems.
Having used Tomcat as an SA and now Java developer I can relate to the parent post.
When I first had to admin Tomcat deployments I found configuring environments very odd. Now that I have to package our products for other SAs I have the feeling that they won't stand much of a chance in changing any live configuration without our guidance. The point is that they should not have to know much about Java to be able to find the correct configuration information.
Our SAs weren't familiar with Apache httpd either but they have taken to that far quicker even though in our environment it is more complex.
I really enjoy working with Tomcat but I can see that it's weirdness may be to my benefit as J2EE SA roles are pretty lucrative at the moment. I'll definately get this book though.
For me, the OSS community is what makes Java such a good platform. There are so many cool tools and APIs. On any one of my projects it seems as if more work has gone in to making the OSS tools that I import than whatever I use from closed packages. It's a shame Sun don't give these developers any credit.
Even though I love Java I don't feel any particular loyalty to Sun and would prefer to not use their products. I just have no idea how near or far GCJ and the GNU Classpath are away from letting me do this.
I've seen that GCJ can produce a natively compiled Tomcat or Eclipse but I'm stumped if I want to natively compile my own 'hello world' example from an ant script.
I think people have grudges against JBoss because of these online forum practices. I've followed a couple of flame wars in the past and believe me, the JBoss guys just do not shut up. I remember looking back at how often they would post and wonder how much spare time they had on their hands - and that didn't include any of these 'anonymous' posts.
They always shoot people down, telling them to put their money where their mouth is but their problem now is that people are actually starting to do this - eg. Geronimo and these blogs.
I still use JBoss as I use JMX heavily, but their online participation has seriously put me off. I only hope that Hibernate doesn't fall to the same standards.
Diesel performance can be very competitive to unleaded these days. Plus, a lot of extra power also seems to be hidden by the ECU. Most modern EU diesels can easily have their ECUs re-mapped to produce an amazing amount of power and can sometimes become _more_ fuel efficient. I've heard of someone doing a constant 100mph and still getting 55mpg.
That said, I totally agree with the black smoke. Part of the road I drive on daily is like a drag strip and these modern performance diesels (BMW/Merc/Audi) chuck out loads of rubbish and it's not nice being behind one. This is why I stick to my 16v 1.2 (remapped) which is a lot of fun for 45mpg.
One of it's advantages is that it can be used outside of a JSP server - so normal applications can use it as a light weight template engine.
Personally I don't like Velocity, but I think it's because I'm in a very XML based environment. As a web presentation layer I use JSTL/taglib and avoid the old school JSP code 'tags'. This way it's closer to XML but I still wish the spec made it fully XML compliant.
When JSPs don't make sense I will always use XSL because the templates can be run on any platform.
Just use common sense!
on
UML Fever
·
· Score: 3, Insightful
How many people use ad-hoc diagrams? Most of the best diagrams I've seen don't follow any standard but do a better job of documenting.
Deployment diagrams are the best example I can think of as they are the most common to not be done in the UML yet they are always easy to understand. (I never could figure out how to describe clustered/redundant/distributed environments with the UML)
I think class and sequence diags are the only ones worth standardizing and I actually like them. Maybe it's coincidence that these are the ones the 'analysts' don't understand.
The only point in standardizing the other diagrams is so that they could be loaded in to any modelling app. Most UML apps don't even agree on what is/isn't UML anyway so why have them?
Some important (I presume) Sun person made the Java on Mars claim at a recent Sun Tech Day. She was quickly corrected by another (more important) Sun guy but it's easy to see how people are getting confused if some Sun sales people are spreading this rubbish.
Slashdot Mirror
Hehe, this is pretty much the opposite of what we actually do. :-P
I work in an organisation where we seem to use PRINCE2 in name only. Once a project is under way the idea of PRINCE2 seems to be to only be concerned about bad things - ie. documentation revolves around things like risk logs and issue logs.
The trouble with where I work is that we bury our heads in the sand when something is wrong. I think this stems from management being scared that if anything bad is documented then it might be used against them. I can kind of see how this might not be so uncommon but would be interested in how this works in a proper environment.
Hehe, having seen some truely awful code where I work (in Java too!) I've always been amazed that our apps run quickly let alone at all. I think unless you are writing some intensive processing loop go for the neat code.
From another point of view though I've always found clever optimisations very interesting (eg. pixel plotting).
is that an average windoze SA or an average Linux SA?
Don't think that by having the word 'enterprise' in the product means there is anything special about it. I've got a bunch of servers with ES pre-installed and it's scary to know that in my 'enterprise' environment I have xeyes and kdegames installed. I could mention _so_ many more....
Basically all RH-ES does (IMHO) is allow companies with FUD-infected management and cowboy SAs to feel happy that they have 'enterprise' Linux systems.
Having used Tomcat as an SA and now Java developer I can relate to the parent post.
When I first had to admin Tomcat deployments I found configuring environments very odd. Now that I have to package our products for other SAs I have the feeling that they won't stand much of a chance in changing any live configuration without our guidance. The point is that they should not have to know much about Java to be able to find the correct configuration information.
Our SAs weren't familiar with Apache httpd either but they have taken to that far quicker even though in our environment it is more complex.
I really enjoy working with Tomcat but I can see that it's weirdness may be to my benefit as J2EE SA roles are pretty lucrative at the moment. I'll definately get this book though.
http://news.bbc.co.uk/1/hi/technology/3962573.stm
For me, the OSS community is what makes Java such a good platform. There are so many cool tools and APIs. On any one of my projects it seems as if more work has gone in to making the OSS tools that I import than whatever I use from closed packages. It's a shame Sun don't give these developers any credit.
Even though I love Java I don't feel any particular loyalty to Sun and would prefer to not use their products. I just have no idea how near or far GCJ and the GNU Classpath are away from letting me do this.
I've seen that GCJ can produce a natively compiled Tomcat or Eclipse but I'm stumped if I want to natively compile my own 'hello world' example from an ant script.
I think people have grudges against JBoss because of these online forum practices. I've followed a couple of flame wars in the past and believe me, the JBoss guys just do not shut up. I remember looking back at how often they would post and wonder how much spare time they had on their hands - and that didn't include any of these 'anonymous' posts.
They always shoot people down, telling them to put their money where their mouth is but their problem now is that people are actually starting to do this - eg. Geronimo and these blogs.
I still use JBoss as I use JMX heavily, but their online participation has seriously put me off. I only hope that Hibernate doesn't fall to the same standards.
Diesel performance can be very competitive to unleaded these days. Plus, a lot of extra power also seems to be hidden by the ECU. Most modern EU diesels can easily have their ECUs re-mapped to produce an amazing amount of power and can sometimes become _more_ fuel efficient. I've heard of someone doing a constant 100mph and still getting 55mpg.
That said, I totally agree with the black smoke. Part of the road I drive on daily is like a drag strip and these modern performance diesels (BMW/Merc/Audi) chuck out loads of rubbish and it's not nice being behind one. This is why I stick to my 16v 1.2 (remapped) which is a lot of fun for 45mpg.
One of it's advantages is that it can be used outside of a JSP server - so normal applications can use it as a light weight template engine.
Personally I don't like Velocity, but I think it's because I'm in a very XML based environment. As a web presentation layer I use JSTL/taglib and avoid the old school JSP code 'tags'. This way it's closer to XML but I still wish the spec made it fully XML compliant.
When JSPs don't make sense I will always use XSL because the templates can be run on any platform.
How many people use ad-hoc diagrams? Most of the best diagrams I've seen don't follow any standard but do a better job of documenting.
Deployment diagrams are the best example I can think of as they are the most common to not be done in the UML yet they are always easy to understand. (I never could figure out how to describe clustered/redundant/distributed environments with the UML)
I think class and sequence diags are the only ones worth standardizing and I actually like them. Maybe it's coincidence that these are the ones the 'analysts' don't understand.
The only point in standardizing the other diagrams is so that they could be loaded in to any modelling app. Most UML apps don't even agree on what is/isn't UML anyway so why have them?
Sorry, should have used highlighting. Read it closely ;-)
This may or may not be what you want to hear but Deus Ex works fine under Wine with full OpenGL support.
It needs no special configuration, it just runs. I've nearly played it half way through again and only come across one little bug.
Before another Wine thread kicks off, then forget it. If you like the game and want to play it you can.
Some important (I presume) Sun person made the Java on Mars claim at a recent Sun Tech Day. She was quickly corrected by another (more important) Sun guy but it's easy to see how people are getting confused if some Sun sales people are spreading this rubbish.