Mike Rozlog

Some walls are necessary. We use brick-and-mortar walls to support buildings and firewalls to protect our computers from attack. But not all walls are good. Consider the Berlin Wall, a wall of segregation. It divided a country and its citizens, but has subsequently been brought down by people working together because upon re-evaluation the Wall did more harm than good. These thoughts led me to think about the walls that developers, QA managers, and database professionals have erected over the years to segregate themselves. Is it time to re-evaluate our own walls? Most organizations, from the small mom-and-pops to the large enterprises, have established all kinds of walls. An example of a good wall is one that is intended to stop or prevent unwarranted access to mission-c... (more)

Software Archeology: What Is It and Why Should Java Developers Care?

The term Software Archeology has been used in various forms since early 2001. The concept of Software Archeology is an approach or methodology that helps individual team members or entire teams to understand exactly what they have in the code they're going to be working on. The approach is also very useful when deconstructing an existing piece of software to find patterns of design and d... (more)

Disaster Recovery Plans Be Prepared

It would seem only logical that after 9/11, one of the most horrific days in American history, corporations large and small would be ready for unforeseen catastrophic events. However, by one recent estimate, less than 38% have put a complete disaster recovery plan in place - the policies, processes, procedures, and architecture to deal with unforeseen events. In the wake of Hurricanes Ka... (more)