Welcome!

Java Authors: Michael Sheehan, Maureen O'Gara, Jonny Defh, Suresh Krishna Madhuvarsu, RealWire News Distribution

Related Topics: Java

Java: Article

The Ideal Way Forward for Software Development

The Ideal Way Forward for Software Development

My mother bought a computer for her birthday, the usual affair – Windows, printer, scanner, speakers, etc. She’s a complete novice and needless to say, she’s having a hard time working the thing. Her main complaint (I think in relation to word processing) is that it does far too many things that she doesn’t want it to do and the terminology is confusing.

I can empathize – as a Java programmer, Integrated Development Environments (IDEs) have, in the past, confounded me in the exact same way, getting in the way of completing the task. These days I’m using a simple text editor with text highlighting for Java programs and Ant, Apache’s Java-based build tool.

I find it much quicker to develop but having said that, I realize there are those who take the time to learn how to “drive” one of these IDEs and swear by them. Maybe I’m just lazy, but I never invested the time and effort into learning the ways of an IDE.

James Gosling recently recognized the fact that there are indeed various levels of developers: people who are not experts at writing code and, presumably, those who are. This is a true observation and IDEs are no doubt a godsend to those who are not experts.

What do the expert code writers think? Do they use these beasts? Often I hear the mumblings, mockings, and dismissals of hard-core engineers as they berate the way of the wizard and gasp in horror at the underlying code it produces. There’s a certain machismo in using a plain text editor to develop software.

Perhaps IDEs are just another step in the journey from the machine languages that Alan Turin (or perhaps Mr. Babbage himself) would have rattled out, and the so-called ease of use of 4G languages and the world of wizards. We don’t have any programming languages that use natural language yet, and if it were possible, would it be desirable?

It seems the entire progress of computer languages is based on the assumption that they should become more like everyday languages (usually English, as fate would have it) and yet it is developers who complain the most about the wizard approach to programming.

Who’s driving this progress? If “hard-core” developers don’t approve of this approach, then who’s behind the demand for tools such as IDEs? Where does Java fit into all of this? Wasn’t Java designed to be easier to learn than its predecessors by extracting a lot of the nuts and bolts away from the developer and utilizing an object-based system?

Industry drives the demand. Industry has a commercial need to utilize the latest in information technology. If this can be made easier and allow more people to become practitioners of languages such as Java, then so much the better – they can have that internal reporting tool up and running in no time at all.

There’s an unnerving contradiction going on here somewhere but I can’t quite put my finger on it. If computer languages are to progress in the same way as they have been, with the honorable goal of expanding the number of programmers, then this could be a problem for developers.

If universities are to continue to churn out conversion course graduates with nine months of experience, will they be as able as the computer scientists? Probably not, but then isn’t that what high-level languages are all about? Making it quicker and easier to learn how to build software.

I seem to have asked more questions than I’ve answered! Oh well! Like I said, I can’t quite put my finger on it.

I’m glad I didn’t get an IDE for my birthday because I would probably be pulling my hair out just like my mother is. How many menus can one piece of software have!

More Stories By Keith Brown

Keith Brown has been involved with Java for many years. When he’s not coding up client solutions for a European Java company, he can be found lurking in the corridors of conferences all around the world.

Comments (1) View Comments

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


Most Recent Comments
scott wills 03/25/02 10:24:00 AM EST

I think the answer you are looking for is nothing new at all, it happens to every profession. Programming is going through the same transition that other professions have gone through in the past. Craftsman are only a temporary phenomenon in any profession. How often do you visit your local blacksmith when you need a new part for your car. When's the last time you went to the carpenter to turn a new leg for a broken chair. Blacksmith's and Carpenter's don't exist anymore. Cars are stamped out by other machines and a whole new chair, assembly line produced, is cheaper than the cost of fixing your broken chair. Software Development is making the same transition. Craftsman are simply too expensive; society cannot afford to have craftsman building everyday items. As soon as a profession is well-enough understood, Engineers will find a way for a machine to replace the craftsman. Blacksmith (or rather Machinist) and Carpenters do still exist, but they are building specialized items. Likewise, some "hard-core" developers do still exist. They are building specialized software. But the bulk of the programmers today are piecing together COTS software and painting screens with IDE's. It's simply the profession transitioning from craftsmanship to assembly line.

The unnerving contradiction is not so much a contradiction, its a realization that you're career is in jeopardy. A few years ago you were probably anxious to jump on the new, latest and greatest technology. Now your a little set in your ways, and that is really hard for a "techo geek" to admit. We are suppose to be out in front on the techno bleeding edge. Past generations, the "old" Blacksmith and Carpenter had experience and wisdom to give him an edge over the energetic youngsters. Change was slow enough that a transition of a profession took a generation or two. Now change is much faster. Our middle aged experience is no match for the new technology in the hands of energitic youth. Improvements in tools are coming too fast. This industry is transitioning to assembly line not in one or two generations. The transition will happen several times over within the span of one career.

You can continue with your text editor - John Henry did beat the steam drill. Of course Mr. Henry died doing it. And a few years later, inevitable, the steam drill replaced hammers and chisels anyway.