Buy Viagra Soft

My news brief on Java Concurrency has been posted on OCI’s site.

Concurrent or multi-threaded software is not a new technology but its importance has been accelerating. This is primarily due to the low cost of multi-core CPUs that are becoming common in even the most basic machines. This trend is expected to continue as hardware manufacturers, following Moore’s law, cram greater numbers of cores onto a single die at ever lower costs. In the past older applications have taken advantage of faster hardware for improved performance, thus extending their functional life. In the future this will be less common because CPUs are not expected to be significantly faster; instead they will be doing more in parallel. There is no better feeling for a developer than knowing that his/her software has withstood the test of time. This is rare, of course, because technology and methodologies don’t remain static but continue to progress with the relentless march of time. It is not advisable to rewrite everything to make use of concurrent algorithms. However, finding places where it makes sense to add multi-threading and “use the right tool for the job” may greatly increase application longevity. It would require a short course to do justice to the topic of concurrent Java development so the remainder of this brief will focus on demonstrating a few of the features with the hope that the reader will continue further study on his/her own.

Read the full article here: Discover the Elegant Simplicity of JSR 166

This is a great article! A must read for those just starting out and a good reminder for those who have learned these lessons the hard way. five habits of highly profitable developers

Great article I found on Digg today. IT Skills You’ll Need in 2010 Don’t leave development yet but one must always think about the future. Make sure that self-improvement continues to be a high priority. Take time to expand and deepen your knowledge of your business and sharpen your soft skills such as writing and speaking. Consider some of the jobs they recommended in the above article, will you be ready to transition into one of them by 2010? Some jobs to consider:

• business enterprise architects
• business technologists
• systems analysts
• project managers

I love my cave! Shut the door and I am in the zone Nerd in a Cave

When starting the next version of a project there are 2 ways to proceed; you can modify and extend your existing application or you can big bang it. For the greatest continuity (confidence and reliability) the only real choice is to extend your existing application. To big bang a project is to acknowledge it’s demise even before it’s started. There have been big bang successes in the past but they are greatly out numbered by those successes which have developed one step at a time. After all, why do you think it’s called development?(not original with me see http://www.paulgraham.com/ and http://www.joelonsoftware.com/) But why do it? Developers have often been stereotyped as those people with the the most optimistic estimates for new work. This is often true, especially of entry level developers who may lack the real world experience to know that their estimates must be padded. At the same time even the most senior developer can become over confident, especially after a series of successes. In general it comes down to an issue of pride (that greatest of sins). As developers we want to make the world in our image and this is our ‘big break’. The world must stand up and take notice! We are an awesome engineer and we can code circles around the next guy…. yeah right. The reality is that we have not taken the time to understand the existing application and all it does. As a result we undervalue the existing work and we underestimate the time it will take to replace it. I blame mental laziness. Don’t let it happen to you.