<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
<channel>
<title>Articles by Joe Winchester</title>
<link>http://eclipse.sys-con.com/</link>
<description>Latest articles from Joe Winchester</description>
<copyright>Copyright 2008 ECLIPSE DEVELOPER&apos;S JOURNAL</copyright>
<lastBuildDate>Fri, 16 May 2008 08:16:00 GMT</lastBuildDate>
<generator>ECLIPSE DEVELOPER&apos;S JOURNAL</generator>
<ttl>10</ttl>
<docs>http://backend.userland.com/rss</docs>

<item>
<title>The 4 Core Principles of Agile Programming</title>
<guid isPermaLink="true">http://eclipse.sys-con.com/read/522904.htm</guid><link>http://eclipse.sys-con.com/read/522904.htm</link>
<pubDate>Thu, 15 May 2008 13:00:00 GMT</pubDate>
<description>One of the things I really enjoy at the moment is the recognition and adoption of agile programming as a fully fledged powerful way to deliver quality software projects. As its figurehead is a group of very talented individuals who have created the agile manifesto (http://agilemanifesto.org/). At its core are four simple principles that, when followed and applied to software projects, generally will ensure a great flexibility and hence higher agility.</description>

</item><item>
<title>Is Computing Riddled with Too Many Acronyms?</title>
<guid isPermaLink="true">http://eclipse.sys-con.com/read/535310.htm</guid><link>http://eclipse.sys-con.com/read/535310.htm</link>
<pubDate>Fri, 04 Apr 2008 11:00:00 GMT</pubDate>
<description>An acronym occurs when the first letters of a phrase are combined into a shortened form that becomes an abbreviated way of describing the original. In science, they are often used to take a fairly verbose and complex concept, such as Light Amplification by Stimulated Emission of Radiation, and create a more concise and catchy noun LASER. The computing world is full of acronyms: Joint Photographic Experts Group becoming JPEG, or Graphics Interchange Format shortening to GIF.</description>

</item><item>
<title>Is It Time for a Hippocratic Oath for Programmers?</title>
<guid isPermaLink="true">http://eclipse.sys-con.com/read/502479.htm</guid><link>http://eclipse.sys-con.com/read/502479.htm</link>
<pubDate>Tue, 26 Feb 2008 08:30:00 GMT</pubDate>
<description>Hippocrates, one of the founding fathers of modern medicine, realized that those who trained to become physicians were not only able to use their skills for good and for progress, but also might be inclined to misuse all they had learned. To protect against such abuses, new grads back in the 4th century B.C. were made to swear they would only use medicine in the best interests of their patients by taking the eponymously named &apos;Hippocratic Oath.&apos;</description>

</item><item>
<title>Google Searching for Java Innovators</title>
<guid isPermaLink="true">http://eclipse.sys-con.com/read/487556.htm</guid><link>http://eclipse.sys-con.com/read/487556.htm</link>
<pubDate>Thu, 31 Jan 2008 15:30:00 GMT</pubDate>
<description>Imagine you are a contestant on a TV game show and your grinning quiz master pops the question: &apos;Name the one thing you most associate with Google?&apos; Think about your answer - write it on a card (don&apos;t show me yet). Turning your card over, it&apos;s likely to be one of the following...Great Internet search engine on google.com; Wicked share price, wish I&apos;d bought some a few years ago; Powerhouse of innovation for Java</description>

</item><item>
<title>Java JVM Swapping - Safe Practice or Unsafe Risk?</title>
<guid isPermaLink="true">http://eclipse.sys-con.com/read/478304.htm</guid><link>http://eclipse.sys-con.com/read/478304.htm</link>
<pubDate>Mon, 24 Dec 2007 23:00:00 GMT</pubDate>
<description>One of the most fundamental design principles of Java is captured in its motto &apos;Write Once, Run Anywhere.&apos; It describes how a .class file encodes its instructions at the bytecode level, allowing portability between different machines that, through a specific virtual machine implementation, resolve the bytecodes into executable instructions to give the program life. It&apos;s a goal that&apos;s almost enshrined in the Java fundamental commandments, as Sun took out a high-profile advertising campaign to back up the &apos;100% Pure Java&apos; slogan and engaged Microsoft in battle for their proprietary language extensions.</description>

</item><item>
<title>Software Salespeople Are Like Pretty Boy Band Members</title>
<guid isPermaLink="true">http://eclipse.sys-con.com/read/464388.htm</guid><link>http://eclipse.sys-con.com/read/464388.htm</link>
<pubDate>Wed, 21 Nov 2007 18:00:00 GMT</pubDate>
<description>Once upon a time, software developers wrote code and ruled their kingdoms. Good programs had few bugs and performed their tasks efficiently and with style. The elite programmers went on to become designers who would lead others in their wake, instilling in them good software practices in a master/apprentice relationship. However, someone was needed to sell the code, so software salespeople were hired who, like pretty boy band members, tended to spend their weekends at the mall browsing shelves of hair products rather than intellectually challenging books.</description>

</item><item>
<title>Pointless Places, Boring Faces, and Useless Cases</title>
<guid isPermaLink="true">http://eclipse.sys-con.com/read/452243.htm</guid><link>http://eclipse.sys-con.com/read/452243.htm</link>
<pubDate>Tue, 30 Oct 2007 16:30:00 GMT</pubDate>
<description>Often in software I find myself preaching restraint to those who wish to move platforms for no apparent reason than to keep up with the IT fashion industry; however, even harder than the silver-bullet chasers is dealing with organizations where change is required, not only in a company&apos;s software stack, but throughout their entire IT department.</description>

</item><item>
<title>Please Listen Carefully as the Following Options Have Changed</title>
<guid isPermaLink="true">http://eclipse.sys-con.com/read/430932.htm</guid><link>http://eclipse.sys-con.com/read/430932.htm</link>
<pubDate>Tue, 18 Sep 2007 11:30:00 GMT</pubDate>
<description>The other day when I arrived at work my phone&apos;s voice mail light was lit up. Cool, except that after pressing the voice mail button I was asked to enter my password. Issac Asimov&apos;s first law of robotics states that &apos;A robot may not injure a human being or, through inaction, allow a human being to come to harm&apos;. Around this time my office mate returns from lunch and inquires why I&apos;m still there given it&apos;s such a nice day outside. The answer is that it was taken away from, me by a robotic system administrator and a fax machine who together, figuratively speaking, ate my lunch.</description>

</item><item>
<title>Doubtful Diagrams and Far Out Figures of Web 2.0</title>
<guid isPermaLink="true">http://eclipse.sys-con.com/read/409116.htm</guid><link>http://eclipse.sys-con.com/read/409116.htm</link>
<pubDate>Tue, 11 Sep 2007 06:45:00 GMT</pubDate>
<description>In a recent presentation I attended, the speaker warmed up with a couple of bulleted lists that outlined the agenda of the session before moving onto his third slide that was clearly many days, work of stitching together powerpoint glyphs and figures in a sort of three dimensional loop that attempted to show the progression of software APIs around the evolution of networked computing.</description>

</item><item>
<title>Desktop Java Slims Down to Enter the AJAX Race</title>
<guid isPermaLink="true">http://eclipse.sys-con.com/read/400081.htm</guid><link>http://eclipse.sys-con.com/read/400081.htm</link>
<pubDate>Wed, 05 Sep 2007 21:45:00 GMT</pubDate>
<description>A number of very significant development efforts are underway that bode well for Desktop Java&apos;s future. On the language side is the Java FX script project http://www.sun.com/software/javafx/index.jsp. Java FX is neat because it provides a high-level scripting interface that runs on top of the Java 2D API. From the users&apos; viewpoint it means they don&apos;t have to write Java code and, for better or worse, understand the intricacies of threads, Java 2D or Swing class hierarchies, timing frameworks, and so forth.</description>

</item><item>
<title>Eclipse Developer&apos;s Journal - The Evolution of Java</title>
<guid isPermaLink="true">http://eclipse.sys-con.com/read/393353.htm</guid><link>http://eclipse.sys-con.com/read/393353.htm</link>
<pubDate>Tue, 03 Jul 2007 07:45:00 GMT</pubDate>
<description>Mike Milinkovich, executive director of the Eclipse Foundation, has been kind enough to answer some questions for Java Developer&apos;s Journal. Rather than rattle off the usual ones about the name, about why Swing wasn&apos;t used, or how much influence IBM still has, Mike has fielded questions on some more current and topical subjects, as well as given us his insights onto the future. Thanks for taking the time to talk to us Mike.</description>

</item><item>
<title>JDJ Editorial &amp;mdash;Conference Presentations, Magic Shows, and the Five-Ring Circus</title>
<guid isPermaLink="true">http://eclipse.sys-con.com/read/393267.htm</guid><link>http://eclipse.sys-con.com/read/393267.htm</link>
<pubDate>Thu, 21 Jun 2007 15:00:00 GMT</pubDate>
<description>Having attended two conferences in the past three weeks and seen untold presentations, I&apos;ve come to the conclusion that irrespective of the subject matter, each presenter invariably falls back on the same technique to impress the audience: to rely on the skills of a conjurer or circus ringmaster as they try to captivate, amaze, and hoodwink their audience.</description>

</item><item>
<title>The Vision for Eclipse: An Interview with Mike Milinkovich</title>
<guid isPermaLink="true">http://eclipse.sys-con.com/read/382948.htm</guid><link>http://eclipse.sys-con.com/read/382948.htm</link>
<pubDate>Sun, 10 Jun 2007 13:00:00 GMT</pubDate>
<description>Mike Milinkovich, executive director of the Eclipse Foundation, has been kind enough to answer some questions for Enterprise Open Source Magazine. Rather than rattle off the usual ones about the name, about why Swing wasn&apos;t used, or how much influence IBM still has, Mike has fielded questions on some more current and topical subjects, as well as given us his insights onto the future. Thanks for taking the time to talk to us Mike.</description>

</item><item>
<title>Intelligent GUIs Should Require No Thought to Operate</title>
<guid isPermaLink="true">http://eclipse.sys-con.com/read/377018.htm</guid><link>http://eclipse.sys-con.com/read/377018.htm</link>
<pubDate>Sat, 02 Jun 2007 20:15:00 GMT</pubDate>
<description>In Bernard J. Baar&apos;s book &apos;A Cognitive Theory of Consciousness,&apos; he describes the brain as having a single conscious area that can be occupied by one thought at a time. The unconscious part of the brain stores memories and experiences and, like the conscious brain, is capable of performing tasks; however, it does so automatically, unlike the conscious area that requires the intervention of the &apos;self.&apos; The first time we are given a new input, sensation, or experience to deal with, the conscious brain is responsible for analyzing it, comparing it to something that has occurred before, and dealing with the action accordingly. Repeated exposure to the same input drives the response into the unconscious area of the mind, so the next time the same experience is encountered, an automatic reply can be recalled without requiring conscious intervention.</description>

</item><item>
<title>Those Who Can, Code; Those Who Can&apos;t, Architect</title>
<guid isPermaLink="true">http://eclipse.sys-con.com/read/345637.htm</guid><link>http://eclipse.sys-con.com/read/345637.htm</link>
<pubDate>Fri, 18 May 2007 23:00:00 GMT</pubDate>
<description>At the moment there seems to be an extremely unhealthy obsession in software with the concept of architecture. A colleague of mine, a recent graduate, told me he wished to become a software architect. He was drawn to the glamour of being able to come up with grandiose ideas - sweeping generalized designs, creating presentations to audiences of acronym addicts, writing esoteric academic papers, speaking at conferences attended by headless engineers on company expense accounts hungrily seeking out this year&apos;s grail, and creating e-mails with huge cc lists from people whose signature footer is more interesting than the content.</description>

</item><item>
<title>Java Editorial &amp;mdash; Not Invented Here: Reject, Repulse, and Reinvent</title>
<guid isPermaLink="true">http://eclipse.sys-con.com/read/366258.htm</guid><link>http://eclipse.sys-con.com/read/366258.htm</link>
<pubDate>Wed, 25 Apr 2007 21:00:00 GMT</pubDate>
<description>The phrase &apos;not invented here,&apos; or NIH, when applied to technology, describes a resistance by a group to use a perfectly valid solution to a problem they&apos;re encountering because they&apos;d rather build the answer from scratch than adopt something existing that already does the job. Assuming that there are no legal or licensing issues to stop the already-built technology from being included, the reasons behind the recalcitrance to its usage usually boil down to human nature.</description>

</item><item>
<title>E-mail -  Problem Solved or Created?</title>
<guid isPermaLink="true">http://eclipse.sys-con.com/read/358080.htm</guid><link>http://eclipse.sys-con.com/read/358080.htm</link>
<pubDate>Mon, 16 Apr 2007 15:00:00 GMT</pubDate>
<description>At the annual Alan Turing memorial lecture given by Grady Booch in London last month, he chose as his subject, The promise, the limits, and the beauty of software. It was an excellent address in which one of the themes was that for each of the incredible advances that software has brought to our lives, there is an almost Newtonian opposite effect that is negative and destructive. One such example given was e-mail: while making us able to communicate instantly with our peers, allowing effective and immediate information sharing, it brings its own set of problems. Issues with information theft, virus attachments, phishing, worms, and privacy are well documented and are very real threats although, to a certain extent, these are merely mirrors of real-world phenomena that e-mail merely amplifies and concentrates. The question that interests me the most is whether e-mail actually increases or decreases communication effectiveness.</description>

</item><item>
<title>Ship Happens! Insights From the Eclipse SWT Community</title>
<guid isPermaLink="true">http://eclipse.sys-con.com/read/345650.htm</guid><link>http://eclipse.sys-con.com/read/345650.htm</link>
<pubDate>Sun, 18 Mar 2007 10:30:00 GMT</pubDate>
<description>The Standard Widget Toolkit (SWT) is the GUI toolkit used by Eclipse. The same folks that worked on the Common Widget (CW) library for IBM/Smalltalk developed it, this time for Java. Now, it&apos;s maintained as part of the Eclipse Platform project and distributed under an open source license, the Eclipse Public License (EPL). One key design point of SWT is that it uses native functionality on each operating system and, at the same time, presents a common, portable API. Joe Winchester, Desktop Java Editor for Java Developer&apos;s Journal, asked Steve Northover (SWT Team Lead) recently whether he&apos;d be happy to answer some questions about SWT and, after talking to his colleagues and a few developers, here is the result.</description>

</item><item>
<title>Software Should Be More Hard Wearing</title>
<guid isPermaLink="true">http://eclipse.sys-con.com/read/325184.htm</guid><link>http://eclipse.sys-con.com/read/325184.htm</link>
<pubDate>Mon, 05 Feb 2007 16:00:00 GMT</pubDate>
<description>I am always in awe of people who develop hardware. They&apos;re the real engineers of our profession, the ones pushing forward the speeds at which things work, their size, and their connectivity. For example, in 2005 there were more computer chips produced worldwide than grains of rice harvested and at a lower unit cost. Tonight as I was watching a movie from the 1980s, instead of dating it by the big hair and shoulder pads, the tree rings were most visible by the size of the mobile phone the hero was using, the lack of a plasma or LCD wide-screen TV in an otherwise luxurious living room, and the absence of a satellite navigation device as the lead characters got lost following directions from a map.</description>

</item><item>
<title>Ten Brilliant Years</title>
<guid isPermaLink="true">http://eclipse.sys-con.com/read/313593.htm</guid><link>http://eclipse.sys-con.com/read/313593.htm</link>
<pubDate>Thu, 14 Dec 2006 12:00:00 GMT</pubDate>
<description>The year 2006 marked the tenth anniversary of the Java language and for me is the most significant in its history. The most important event was the announcement that a GPL version of Java SE will be available sometime in the first half of 2007. If nothing else, all the back and forth &apos;will they, won&apos;t they&apos; discussions over open source have been a distraction for the Java community.</description>

</item><item>
<title>The Two-Dimensional Legacy of GUIs</title>
<guid isPermaLink="true">http://eclipse.sys-con.com/read/299971.htm</guid><link>http://eclipse.sys-con.com/read/299971.htm</link>
<pubDate>Thu, 30 Nov 2006 09:00:00 GMT</pubDate>
<description>Ted Nelson, inventor of, among other things, hypertext, once lamented that software development today is at the same evolutionary stage film making was at 100 years ago. Back in the 1900s, when the technology of film production was in its earliest stages, the cameraman was the person in charge because he was the one who understood the technology and could make it function correctly. The audience&apos;s sheer fascination with the magic of films was enough to captivate and hold their attention while the silent and blurred subjects grinned and gawked directly into the lens. Much has changed in the last hundred years though, and movie directors are now the ones in charge of making a film.</description>

</item><item>
<title>The Perils of Abstraction</title>
<guid isPermaLink="true">http://eclipse.sys-con.com/read/286909.htm</guid><link>http://eclipse.sys-con.com/read/286909.htm</link>
<pubDate>Sun, 05 Nov 2006 14:00:00 GMT</pubDate>
<description>Abstraction, as defined on dictionary.com, is &apos;considering something as a general quality or characteristic, apart from concrete realities, specific objects, or actual instances.&apos; It&apos;s a powerful concept that underpins software reuse. When you implement a problem, if, instead of starting from scratch, the scenario can be thought of as being an example of an already-understood question, its solution can benefit from existing implementations.</description>

</item><item>
<title>NetBeans Interview with Tim Cramer</title>
<guid isPermaLink="true">http://eclipse.sys-con.com/read/286891.htm</guid><link>http://eclipse.sys-con.com/read/286891.htm</link>
<pubDate>Mon, 23 Oct 2006 07:00:00 GMT</pubDate>
<description>Recently I was able to talk to Tim Cramer, executive director of tools at Sun, about NetBeans. Tim started in engineering doing supercomputer compiler work, moved to more generalized hardware compiler work, and naturally moved to JIT/dynamic compilers in Java during its first few years. Tim&apos;s first management job was in the Java performance group, working to improve the base performance of Java SE and EE. He followed as the director of NetBeans in August of 2004 and is now the executive director for all Java tools at Sun.</description>

</item><item>
<title>Java: Money, Freedom and Open Source</title>
<guid isPermaLink="true">http://eclipse.sys-con.com/read/273983.htm</guid><link>http://eclipse.sys-con.com/read/273983.htm</link>
<pubDate>Thu, 28 Sep 2006 17:30:00 GMT</pubDate>
<description>In 1996, Sun created Java and the terms under which it is distributed. Since then, the Java Community Process (JCP) has emerged, allowing companies to participate in shaping language changes, but the ownership of trademarks, licensing agreements, branding, and other fundamental product issues remains unchanged. One is reminded of this fact every time the Sun MicrosystemsTM trademark appears alongside the Java coffee cup logo, or when one is greeted with the message &apos;brought to you by Sun Microsystems&apos; at www.java.com. For anyone to use the Java-compatible logo on a product requires verification against the test compatibility kit (TCK), for which one has to enter into negotiations with Sun. Java, the technology, the trademark, and the language, are owned by Sun.</description>

</item><item>
<title>The Death of Mediocrity</title>
<guid isPermaLink="true">http://eclipse.sys-con.com/read/260060.htm</guid><link>http://eclipse.sys-con.com/read/260060.htm</link>
<pubDate>Wed, 30 Aug 2006 11:00:00 GMT</pubDate>
<description>Computers can generally be characterized into two types: ones that are designed to have more than one user attached and those intended for a single user. In the beginning almost all computing was done on large multi-user machines, partly due to their expense, which precluded their use to all but large institutions or wealthy corporations. Mainframes ruled this era and excelled at their role: providing a reliable computing platform for hosting databases, transaction servers, and centralized applications. The interaction was through character-based screens that, while providing fast and efficient green screen access, was to be their Achilles heel.</description>

</item><item>
<title>Can Map Do A Better Job at Allowing Optimized Iteration Over Its Keys and Values Together?</title>
<guid isPermaLink="true">http://eclipse.sys-con.com/read/260997.htm</guid><link>http://eclipse.sys-con.com/read/260997.htm</link>
<pubDate>Tue, 15 Aug 2006 17:00:00 GMT</pubDate>
<description>I&apos;ve used the map to store things in a keyed fashion and want to iterate over the keys and the value for each. Problem is, each time I do it I find myself thinking how inefficient it must be. The keys iterator returns the keys so it has to walk the keys, however the get(key) has to lookup the key each time.Internally implementations like HashMap store keys and values as linked list pairs</description>

</item><item>
<title>Who Does Business Logic?</title>
<guid isPermaLink="true">http://eclipse.sys-con.com/read/250273.htm</guid><link>http://eclipse.sys-con.com/read/250273.htm</link>
<pubDate>Mon, 31 Jul 2006 15:15:00 GMT</pubDate>
<description>One of the phrases that has always puzzled me is &apos;business logic&apos;. It seems to crop up a lot in presentations, articles, sales pitches and so forth.  The one I saw it in most recently was a talk about how great web servers are because they keep all of the business logic on the server where it can be robust, secure, and logged.  By analogy the client is a poor place for business logic because, while it can do richer things with the user interface, all of the core rules must be kept on the server.</description>

</item><item>
<title>SPAM, FUD and Rogue Web Services</title>
<guid isPermaLink="true">http://eclipse.sys-con.com/read/242174.htm</guid><link>http://eclipse.sys-con.com/read/242174.htm</link>
<pubDate>Wed, 28 Jun 2006 16:30:00 GMT</pubDate>
<description>First one today from &apos;Visa services&apos; who&apos;d insisted I entered my credit card details and password on their web site today to avoid irreversible instant deactivation of my account. Only problem is I don&apos;t have a Visa card and their URL had a Zambian IP address so I quickly deleted it.Next suspect in-box entry was claiming to be from a lawyer for a rich deceased ex-president who needs my help moving millions of pounds to Europe; the title of which was &apos;Can you be trusted ?&apos;.  This type of scam is the well documented 491 variant of the centuries old Spanish Prisoner con, and is the subject of the extremely funny book &apos;Tuesdays with Mantu: My Adventures with a Nigerian Con Artist&apos;</description>

</item><item>
<title>Rich Client, Poor Client, Cool Client, AJAX</title>
<guid isPermaLink="true">http://eclipse.sys-con.com/read/164233.htm</guid><link>http://eclipse.sys-con.com/read/164233.htm</link>
<pubDate>Tue, 27 Jun 2006 13:30:00 GMT</pubDate>
<description>The problem with the web has always been that despite anyone trying to convince you otherwise, it&apos;s a page based latency bound transaction model that is a dressed up graphical mainframe. Works well because the transport protocol is neutral and ubiquitous allowing heterogeneous end points where the client and server don&apos;t have to know all that much about each other, just how to establish an HTTP connection.  Problem with web is that if all the logic occurs on the server back end app, then the client is relegated to being just a dumb renderer of HTML, which sort of belittles the fact that PCs are pre-emptive multi-tasking box with oodles of processing power.</description>

</item><item>
<title>Swing Baby, Yeah!!!</title>
<guid isPermaLink="true">http://eclipse.sys-con.com/read/232079.htm</guid><link>http://eclipse.sys-con.com/read/232079.htm</link>
<pubDate>Tue, 20 Jun 2006 15:30:00 GMT</pubDate>
<description>Back in 1996, Java was originally hailed as a way of making the Web more appealing through applets, and, with its &apos;write one, run anywhere&apos; philosophy, as the holy grail for desktop apps that would be truly cross platform. The truth is that both were oversold at the time. With the combination of low bandwidth Internet connections and early Swing releases not living up to user expectations occurring in the middle of the Microsoft vs. Sun &apos;pure Java&apos; fight that resulted in JVMs being pulled from Internet Explorer, Java&apos;s attention moved off the desktop and onto the server.</description>

</item><item>
<title>Web 3.0 - The Lunatics Have Taken Over the Asylum</title>
<guid isPermaLink="true">http://eclipse.sys-con.com/read/226482.htm</guid><link>http://eclipse.sys-con.com/read/226482.htm</link>
<pubDate>Wed, 24 May 2006 10:30:00 GMT</pubDate>
<description>When the phrase Web 2.0 came out a number of people were sceptical about what it actually means. Being objective, it&apos;s a collection of disparate technologies that make web sites more usable. Everyone wants their user interfaces to look and work better, and most of web developers&apos; energy over the last decade has been spent focusing on the former. It seems that recently however they&apos;ve decided that it&apos;d be nice to make them actually more usable.</description>

</item><item>
<title>Java Developer&apos;s Journal: &apos;To Dwell in the Future and Forget About Today&apos;</title>
<guid isPermaLink="true">http://eclipse.sys-con.com/read/216380.htm</guid><link>http://eclipse.sys-con.com/read/216380.htm</link>
<pubDate>Mon, 22 May 2006 09:15:00 GMT</pubDate>
<description>Some of the words I dread most in a meeting are: &apos;What if ?&apos; They&apos;re fine in the present tense of &apos;What if a user tries this option?&apos; or &apos;What if the database read fails mid flight?&apos;, but as soon as the future tense is introduced I begin to worry. &apos;What if the database and middleware changes?&apos; or &apos;What if sometime soon we don&apos;t just have to run on PCs but need to work on mobile phones?&apos; There is also the future future tense such as &apos;What happens to the UI if the operating system is ported to run on a wrist watch?&apos; or &apos;What if one day the company merges with another whose corporate standard is MAC and SNA?&apos;</description>

</item><item>
<title>All for One and None for All</title>
<guid isPermaLink="true">http://eclipse.sys-con.com/read/204718.htm</guid><link>http://eclipse.sys-con.com/read/204718.htm</link>
<pubDate>Tue, 25 Apr 2006 11:00:00 GMT</pubDate>
<description>When someone in a corporate boardroom decides what their IT strategy is going to be, it isn&apos;t based on what language or software architecture they will use, but on how a system can provide value to their business. Very few organizations buy their hardware and OS first, and then tool up to write a bespoke solution that meets their business needs. In my first job I worked for a software house that built specialized insurance applications. Companies put out tenders for business that we responded to, and whether our products or a competitors&apos; were chosen was based on the value proposition in the boardroom. The hardware, platform, and application server were dragged into the sale because they were required by the solution, but the app was always the endpoint that drove the purchase.</description>

</item><item>
<title>Web Services and SOA - Sexy Clients and Programatic Oaths</title>
<guid isPermaLink="true">http://eclipse.sys-con.com/read/208498.htm</guid><link>http://eclipse.sys-con.com/read/208498.htm</link>
<pubDate>Tue, 18 Apr 2006 13:45:00 GMT</pubDate>
<description>Recently I was called in at the last minute to help out with a sales opportunity. The team had been working hard on a proposal for many months, during which they&apos;d built a large working prototype system that talked to the customer&apos;s actual back end systems using web services and SOA. To their surprise however it had been slammed in the demos, because the user interface (the last part the sales team had put together) had been thrown together using just default fonts and colors, and basic text boxes and buttons.</description>

</item><item>
<title>We Are Made to Persist. That&apos;s How We Find Out Who We Are</title>
<guid isPermaLink="true">http://eclipse.sys-con.com/read/192453.htm</guid><link>http://eclipse.sys-con.com/read/192453.htm</link>
<pubDate>Wed, 22 Mar 2006 14:00:00 GMT</pubDate>
<description>In Java&apos;s early years, the language received a lot of flak from its opponents over performance. Java turns its .class file bytecodes into machine instructions (MI) at runtime, something that costs cycles and is slower than a fully compiled language that creates the MI as part of the development stage. While to a certain extent this is true, the performance delta has all but been removed with the use of just-in-time (JIT) compilers that cache machine instructions in the VM and do other clever tricks to ensure the JVM runtime speed has very little slack. There was a time when JIT had to be switched off for debugging as it interfered with the ability to map stack and heap information back to the original source. However, even this is no longer true in the newer JVMs that can run in high-performance debug modes with no significant difference between having -Xdebug there or not.</description>

</item><item>
<title>Where Are the High-Level Design Open Source Tools for Java?</title>
<guid isPermaLink="true">http://eclipse.sys-con.com/read/180409.htm</guid><link>http://eclipse.sys-con.com/read/180409.htm</link>
<pubDate>Mon, 27 Feb 2006 13:15:00 GMT</pubDate>
<description>I have just finished reviewing the book Open Source Development Tools for Java, which provides excellent coverage of such topics as log4J, CVS, Ant, and JUnit. There is a chapter on UML tools though in which the author almost apologizes for the lack of good open source design tools. There is a plethora of projects on SourceForge.net from J2EE runtime frameworks to IDE plugins, yet there is almost nothing that encroaches upward into the arena of analysis and design tools.</description>

</item><item>
<title>When Fixing Problems, Look Beyond</title>
<guid isPermaLink="true">http://eclipse.sys-con.com/read/171496.htm</guid><link>http://eclipse.sys-con.com/read/171496.htm</link>
<pubDate>Thu, 09 Feb 2006 09:00:00 GMT</pubDate>
<description>One way in which technology is adopted is when an existing process is automated and made more efficient, cheaper, or reliable. Another is when a technique or innovation is applied to an existing process to drastically alter the way it occurs. The disadvantage of the latter is that it requires the idea being sold to someone who has to change to adopt it, and thereby carries a risk of failure. Applying a technology to merely streamline an existing process is a simpler to adopt as the implementation merely involves oiling an existing solution.</description>

</item><item>
<title>Joe Winchester&apos;s Java Blog: Is the AJAX Bullet Coated in Fool&apos;s Silver?</title>
<guid isPermaLink="true">http://eclipse.sys-con.com/read/175805.htm</guid><link>http://eclipse.sys-con.com/read/175805.htm</link>
<pubDate>Thu, 26 Jan 2006 11:15:00 GMT</pubDate>
<description>Ajax is an odd beast, because it gives a very rich user experience when compared to a traditional web page (Yakov writes wonderfully about this at http://java.sys-con.com/read/163232.htm), however apart from that it?s hard to figure out what is so great about it. Good technology wins in the long run because of tooling (something Microsoft know and excelt at), so what is the lure of Ajax? I think it?s simply that it allows logic be put in one file ? in your HTML (or servlet, JSP, ASP or whatever kicks out HTML) you write your server logic and your client logic together.</description>

</item><item>
<title>i-Technology Viewpoint: Java&apos;s Not Evolving Fast Enough</title>
<guid isPermaLink="true">http://eclipse.sys-con.com/read/163294.htm</guid><link>http://eclipse.sys-con.com/read/163294.htm</link>
<pubDate>Mon, 09 Jan 2006 05:15:00 GMT</pubDate>
<description>&apos;If Java is to remain at the forefront of technology for the next 10 years,&apos; writes Joe Winchester in his Java Developer&apos;s Journal column, &apos;it needs to find a way of decoupling API calls between internal code and external blocks, perhaps even introducing soft typing calls across program boundaries or having flexible message transport across modules.</description>

</item><item>
<title>Joe Winchester&apos;s Java Blog: No More J and No More 2</title>
<guid isPermaLink="true">http://eclipse.sys-con.com/read/151052.htm</guid><link>http://eclipse.sys-con.com/read/151052.htm</link>
<pubDate>Sun, 04 Dec 2005 11:15:00 GMT</pubDate>
<description>Rumors of this name change have been flying around for a while but it is now official - the brand has been kicked into the bucket and replaced instead with a more verbose name and &apos;Platform.&apos; This probably isn&apos;t such a bad thing. The 2 was sort of a year 2000 thingy (see Calvin Austin&apos;s JDJ March editorial for the reason behind its name), and as such does feel rather dated.</description>

</item></channel></rss>