SmallThoughts - Computers, Programming Languages and Technologies

A class with the public modifier gives to all classes in all packages access to it. In other words, all classes can instantiate, extend or return a class of that type. Example:

package humanity;
public class Person {}

This class is visible to all classes in all packages. But if this class is in a different package, we need to import it yet.
Some exceptions exists, mainly when we use the nonaccess final modifier. I will explain soon.

Ok, my most boring post until now. Don’t forget these Java keywords and reserved words:

A class with default access has no modifier preceding it in the declaration. The default access is a package-level access, because a class with default access can be seen only by classes within the same package. If a class has default access, a class in another package won’t be able to create a instance of that class, or even declare a variable or return type. The compiler will complain. For example:

package humanity;
class Person {}

package family;
import humanity.Person;
class Child extends Person {}

Try to compile this 2 sources. As you can see, they are in different packages, and the compilation will fail.

After thinking a lot about, I take a decision: I will take some certification exams in the Java Language. My object is to take the entry lavel exam Sun Certified Java Programmer (SCJP), and after follow the path until the Sun Certified Enterprise Architecture (SCEA).
I will try to put some notes here, about what I learn while chasing this objectives.
The book Sun Certified Programmer & Developer for Java 2 Study Guide (Exam 310-035 & 310-027) will be my partner for the next months. I will try to get my Java Black Belt, while I too do some mock exams. Cross your fingers!

When I´m again starting a new mega-over-ambitious web project, I ask myself the same question: “What´s is the f&*%ing reason for doing a web oriented project, if this project should be a very tiny, nice desktop project”? Maybe because doing it in a web way is sexy, a tech fashion. Maybe I´m starting to become a old guy with old ideas, but when we stop to ask reasons and start to do things using “best practices” or “experts recommendations” without thinking about, something is very wrong.
Some great pros of thin clients are low deployment costs, low hardware requirements, distributed and parallel platform almost for free.
Some cons of web solutions: the everyday fight against the HTTP stateless protocol, the browsers lack of standards.
Some pros of rich clients: rich user experience (you are in control of every pixel on the screen).
But there are great means to low the deployment cost of desktop applications. The Java Web Start Technology is under used, but a great to glue all together.
The nature give the most simple answer which works, and in development isn´t different. If the desktop development was the first to appear, it was because
it is the most simple solution which works. The tendency to create only web applications today is increasing the projects costs,
and helping its younger death.
When starting a new project, think about. What your opinion?

Great RCP toolkits for Java: Netbeans and Eclipse.

Great Web applications for Java which FAKE a desktop: WingS and Echo2.

Why we yet suffer with browsers which doesn´t support web standards?
There are standards, and the responsible organization is the W3C .
If your browser doesn´t follow web standards, complain with your browser supplier, don´t curse the poor web designer, who did a good work learning, researching, to make a modern web site. Welcome to the 21st century. There a list of browsers to you make a upgrade.
If you are starting a new web project, and your manager or client aren´t aware of standards, caution! Stop everything, explain the reasons, there is a lot of them around.

I already worked in very poor standarlized projects. I konw what I´m saying.

My 2 cents.

Here are some books I’ve read that I’m recommending. I choose these books because all of them talk about computer science, software modeling or software engeneering, and all software developers can benefit from each of these books, whatever your programming language is.

So here, in no particular order…

This book have a lot of “Solved Problems” to add to your personal “Mental Library”.

Analysis Patterns: Reusable Object Models (The Addison-Wesley Object Technology Series)

Edsger Dijkstra once wrote:

To my reader.
These notes have the status of Letters written to myself. I wrote them down because, without doing so, I found myself repeating the same arguments over and over again. When reading what I had written, I was not always too satisfied.
Notes on Structured Programming

I don t want to compare myself to this genius who wrote much of the today computer science. But I hope to give to this blog the same meaning, the same soul.

Welcome all readers.