Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
Check out the new SourceForge HTML5 internet speed test! No Flash necessary and runs on all devices. ×

Comment firefighting app (Score 1) 630

I agree that software needs more focus, though it's harder to paint a quick picture in people's minds unless you say something like "make more apps."

I was actually very pleased that he used the example of firefighters downloading building plans on their way to a fire on their "PDA", since that's an app I actually built a few years ago (and current client ... http://getblazemark.com/

Focus depends on ease and effectiveness of narrative. If you can't get a hit in 10 seconds, it won't give the punch.

Comment Re:Do No Evil (Score 1) 224

There's two opposing groups to reckon with here: the employees and the shareholders. The latter wants the highest profit.

So as a "good" corporate manager, which group are you kind to? The only real answer for the shareholder side is ... maximize profits until morale/turnover sinks to the point where product (and profits) suffer. Any further spending for the employees is a negative for the shareholders.

Or you can sway the balance to treating your employees better for other than profit motives ... good PR, good retention, higher creativity/productivity. Again, unless these translate into better revenues, it's taking away from the shareholders.

UNLESS ... the shareholders, as a group, also want to "do good" and treat employees better than the bottom dollar.

It's about the shareholders, not the managers.

Comment Java EE 6 (Score 1) 519

Having just finished a non-trivial project using Java EE 6, I'm very pleasantly surprised at how far things have progressed in the Java world.

I used:

* Glassfish (app server)
* JPA 2 (EclipseLink)
* JSF 2 (Mojarra)
* EJB 3.1
* PrimeFaces (excellent JSF toolkit)
* Selenium/JUnit/Maven, etc.
* Java 6+

Java EE 6 completes the job started in Java EE 5, which is essentially ... re-do everything using the best practices developed in the last 10 years, learning from everyone's new ideas and jettison'ing the old. Convention over configuration, annotations, streamlining ... all decent throughout.

Standard Java EE is now very robust, speeds development, assures safety, and aids test-driven development.

I also think this particular stack will hang around for a good number of years, if not decades. They finally got it right.

Slashdot Top Deals

"The chain which can be yanked is not the eternal chain." -- G. Fitch

Working...