AGILA

1. Learn english. Your english has not to be perfect, yet you should be able to read english Java literature and to write a little english documentation (aka javadoc) for the software you are developing.
2. Learn the basics. You should know what Java interfaces are, how generics work, and so on. That means, beside your programming skills you should know some theoratical aspects about Java.
3. Take one of the frameworks, tools, libraries, or whatever, and learn as much as possible about it. Then move to the next framework, tool, or whatever… In that way you will gather a lot of knowledge over time.

Read the rest of this entry »

Generic type := type with formal type parameters.

The type is not a Throwable or a subclass of Throwable, an enum types, or an anonymous inner class.

Type parameter := a place holder for a type argument.

Parameterized type := instantiation of a generic tpye with actual type arguments.
Read the rest of this entry »

Let’s assume you are a software developer, a free-lancer, and a prospect customer calls you. He needs a (small to medium-size) Web application and wants you to develop that application, but first he asks for the best “technology” for that application. What do you say?

Yes, what kind of useful technologies are there? And what are the criteria to select one?

You do not use Microsoft technologies, because you are a Java developer… Maybe MS would have some useful tools for the job, but you don’t know them or don’t want to use them.

So what about php? The big advantage is that it runs on a lot of servers, doesn’t need many resources, and there is much code available on the Web. But still, you are a Java delopver. And the customer wants a rich user experience, i.e. you will need a lot of JavaScript in the application. Or maybe there’s something else?

Read the rest of this entry »

HttpCore and HttpClient are now available in a 4.0 version. It’s not ready for “production” yet, but it’s going in the direction of an improved API and better performance.

“HttpClient now sports a cleaner, more flexible and expressive API, a more modular structure, improved performance and reduced memory footprint. [..] HttpClient 4.0 is still considered experimental and should be used with caution.” Changes in HttpClient 4.0

Home Page of HttpClient