AGILA

Google App Engine gives you the possibility to write Web applications and to deploy them on Google servers, so that those applications are very secure, fast, and especially very scalable. Currently it is still in the test phase, but as soon as that application platform will be released, it will probably perform very well.

So is this cool? It is. Read the rest of this entry »

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 »

The project managers of the projects I work for can be classified into two groups: either they say quality comes later, first we have to finish the project, i.e. to implement all the functionality. Or the say, we want to make it right from the beginning, implement in a more quality conscious way, and hope that we will finish the project on time.

Read the rest of this entry »