The case with being an expert on one thing vs. being a jack of all trades

with regards to being a software engineer, i would say that being an "expert"
or at least to be able to really have an in-depth above average knowledge/experience/skill
on a specific domain/context is a must. For example, one could be an expert developing
on banking enterprise web applications using java. Expertise or at least an in-depth above
average skill would be necessary for a good software engineer to be able to deliver with
flying colors. Otherwise, the product would not be as good. This is whether one is working
with a team or not. On the other hand developing an enterprise web application using java
would require other skills as well like database, connection and object pooling, sometimes
LDAP, web services, etc. Whether the software engineer is working with a team or not
and whether these different skill requirements are delegated to others, still the software
engineer would do him his own good if he at least knows a basic average knowledge for the
different skill requirements (jack of all trades). It is important to point out that IMO
it would be best to have these basic average knowledge skills wherein these skills are
connected to the expertise that the engineer is delving himself into.

An Android Todo List Program

I am now starting development on my very own android todo list program (the official name of the program will be disclosed in the future).. it will have a todo list of course, and it will also come with alarms, calendar event markings, goals, and other features as well..

My Fave Java Sites

1. http://www.java-tv.com
2. www.javaranch.com
3. www.javalobby.org
4. www.onjava.com
5. http://java.sun.com
6. http://www.devx.com/java
7. http://www.theserverside.com
8.

Why I would always love Eclipse over Netbeans

This is because when it comes to IDEs I will always choose the one that provides me with the best productivity but will least get in my way of software development. Netbeans, although RAD (I think it's too much RAD and FAD though) with its multitude of auto-generation and wizardry just gets in my way because it produces artifacts and codes that are not standards. In other words, it creates files that are netbeans specific. Like if you use the Visual drag and drop for its Java Server Faces, I doubt if anyone have actually used it on production projects. I hate it. Eclipse forever. Heheh.