During the last week I had to interview five developers for a position that
required the following skills: Flex, Java, Spring, and Hibernate. Most of
these guys had demonstrated the 3 out of 10 level of Flex skills even though
each of them claimed a practical experience on at least two projects. But
this didn’t surprise me – Flex is still pretty new and there is only a
small number of developers on the market who can really get Flex things done.
What surprised me the most is a low level of Java skills of most of these
people. They have 5-8 years of Java EE projects behind their belts, but they
were not Java developers. They were species that I can call
Robot-Configurator. Each of them knew how to configure XML files for
Spring, they knew how to hook up Spring and Hibernate and how to map a Java
class to a database entity. Some of them even knew how to configure laz... (more)
Graphical user interface (GUI) testing is a potentially problematic area
because constructing effective test cases is more difficult than the
corresponding application logic. The roadblocks to effective functional GUI
Traditional test coverage criteria like "80% coverage of the lines of code"
may not be sufficient to trap all the user interaction scenarios. End users
often use a different user task interaction model than the one conceived by
the development team.
Functional GUI testing needs to deal with GUI events as well as the effects
of the underlying applicati... (more)
Last month, JavaBlackBelt completed a survey where developers said their
teams would be 25% more productive if their management committed to skills
management... which led me to consider:
Which Java technologies do developers think that managers should understand
better in order to make great decisions about skills management?
I'll suggest, as a start:
-- Java SE and EE basics
-- ORM's (Hibernate, ...)
-- Web Frameworks (lStruts 2, ...)
-- IDEs (Eclipse, ...)
-- Source Code Mgmt
-- Testing Methods
Very open to your thoughts, and who might find such a course usef... (more)
We can visualize resource starvation using an elaborate rendition of the
Dining Philosophers Problem. This classic metaphor of resource allocation
among processes was first introduced in 1971 by Edsger Dijkstra in his paper
"Hierarchical Ordering of Sequential Processes." It's been a model and
universal method for verifying theories on resource allocation ever since.
The metaphor goes like this: There are three well-known philosophers in an
Asian bistro. Dinner is served but they are only given three chopsticks
because the restaurant's supply truck has been stuck in a snow storm f... (more)
JavaBlackBelt just announced its “Coached e‐Learning” for Java
In a developer survey to be released next week, this Coached e‐Learning was
selected as the #1 choice for Java learning compared with classroom training
and self‐paced e‐Learning.
Here’s how it works:
1. In these courses, the coach meets with the student to begin each course,
reviews the course plan and materials, and agrees to a schedule.
2. The student then learns at their own pace from the JavaBlackBelt eLearning
platform ‐‐ online materials and videos, community forums, exercises, and
3. Alon... (more)
This article tries to demonstrate that Java can be more productive than Ruby.
We are going to develop the same application of the article Rolling with Ruby
on Rails Revisited (part 1  and part 2 ) but using POJO s annotated
with JPA  and a Model Driven Framework, OpenXava  in this case. The
result is that with less code, and less time you obtain a more powerful
Ruby and rails: The regressive framework
Ruby on rails  is so elegant, so easy, so productive. I cannot avoid read
and heard continuously these comments. For example, the article Rolling with ... (more)