Object Mentor Blog: There will be code

There will be code

Uncle Bob — Thu, 28 Aug 2008 21:02:45 -0500

During the last three decades, several things about software development have changed, and several other things have not. The things that have changed are startling. The things that have not are even more startling.

What has changed? Three decades have seen a 1000 fold increase in speed, another 1000 fold increase in memory. Yet another 1000 fold decrease in size (by volume), and yet another 1000 fold decrease in power consumption. Adding up all those zeros implies that the resources we have to play with have increased by twelve orders of magnitude. Even if I have over estimated by five orders of magnitude the remaining seven are still and astounding increase.

I remember building RSX-11M on a PDP-11/60 from source. It took several hours. Nowadays I can build huge java applications in a matter of seconds. I remember that compiling small C programs required dozens of minutes. Now much larger programs compile in a eyeblink. I remember painstakingly editing assembly language on punch cards. Now I use refactorings in huge java programs without thinking about it. I remember when 10,000 lines of code was five boxes of cards that weighed 50 pounds. Now, such a program is considered trivial.

Nowadays we have tools! We have editors that compile our code while we type, and complete our thoughts for us. We have analyzers that will find code duplication in huge systems, and identify flaws and weaknesses. We have code coverage tools that will tell us each line of code that our unit tests fail to execute. We have refactoring browsers that allow us to manipulate our code with unprecedented power and convenience.

But in the face of all this massive change, this rampant growth, this almost unlimited wealth of resources, there is something that hasn’t changed much at all. Code.

Fortran, Algol, and Lisp are over fifty years old. These language are the clear progenitors of the static and dynamic languages we use today. The roots of C++, Java, and C# clearly lie in Algol and Fortan. The connection between Lisp, and Ruby, Python, and smalltalk may be less obvious, but only slightly so. Today’s modern language may be rich with features and power, but they are not 12 orders of magnitude better than their ancestors. Indeed, it’s hard to say that they are even ONE order of magnitude better.

When it comes down to it. We still write programs made out of calculations, ‘if’ statements, and ‘for’ loops. We still assign values into variables and pass arguments into functions. Programmers from 30 years ago might be surprised that we use lower case letters in our programs, but little else would startle them about the code we write.

We are like carpenters who started out using hammers and saws, and have progressed to using air-hammers and power saws. These power tools help a lot; but in the end we are still cutting wood and nailing it together. And we probably will be for the next 30 years.

Looking back we see that what we do hasn’t changed all that much. What has changed are the tools and resources we can apply to the task. Looking forward I anticipate that the current trend will continue. The tools will get better, but the code will still be code. We may see some “minor” improvements in languages and frameworks, but we will still be slinging code.

Some folks have put a great deal of hope in technologies like MDA. I don’t. The reason is that I don’t see MDA as anything more than a different kind of computer language. To be effective it will still need ‘if’ and ‘for’ statements of some kind. And ‘programmers’ will still need to write programs in that language, because details will still need to be managed. There is no language that can eliminate the programming step, because the programming step is the translation from requirements to systems irrespective of language. MDA does not change this.

Some folks have speculated that we’ll have “intelligent agents” based on some kind of AI technology, and that these agents will be able to write portions of our programs for us. The problem with this is that we already have intelligent agents that write programs for us. They are called programmers. It’s difficult to imagine a program that is able to communicate to a customer and write a program better than a human programmer.

So, for the foreseeable future I think software will remain the art of crafting code to meet the requirements of our customers.

There is something else that needs to change, however. And I believe it is changing. Our professionalism.

In some ways our “profession” has paralleled that of medicine. 300 years ago there were a few thinkers, and far too many practitioners. There were no standards, no common rituals or behaviors, no common disciplines. If you got sick you might go to a barber, or a healer. Perhaps he’d let out some blood, or ask you to wear some garlic. Over time, however, the few thinkers gained knowledge, discipline, and skill. They adopted standards and rituals. They set up a system for policing and maintaining those standards, and for training and accepting new members.

THIS is the change that I hope the next thirty years holds for software development.

"There will be code" by wholesale new era hat

Mon, 12 Dec 2011 20:17:30 -0600

The September downgrades were due to the bank’s exposure to Greece in the case of Credit Agricole, and Moody’s view that the bank no longer enjoyed the same level of government support in the case of Societe General.http://www.wholesalenewerahatscaps.com/

"There will be code" by ysbearing

Wed, 19 Oct 2011 03:28:33 -0500

Slewing ring is also called slewing bearing, some people called: rotary support, swing support. English Name: slewing bearing or slewing ring bearing or turn table bearing, slewing ring in the real industrial applications is very wide.

"There will be code" by cheap tisa snapbacks

Fri, 07 Oct 2011 04:49:19 -0500

This is a major problem. Whatever selection The united states prefers this kind of Late may gain not just the legal right to oversee the country, he’ll have got our prime freedom with losing the earliest frequency as soon as the The year just gone soccer period commences.Purportedly,discount designer handbag the next web design manager could have your available funds with an real built in 59fifty limit, rather than the great buy style demonstrated here. I bought this cap at a Wal-Mart inside The year 2005 if your Nation’s Group expanded to include the actual Nats.I used to be happy how the operation brought back the actual vintage software ???W using a reddish colored cap,gucci scarf identical to your style worn with the California Senators associated with my children’s.People ended up being a hapless Senators 2.0, the actual operation in which had become the Tx Ranger. The initial Senators bolted a Area associated with The philipines prior to along with had become the Minnesota Mixed twins.I have dug online diligently intended for photos involving McCain as well as Obama dressed in cheap tisa snapback hats, and i seemed to be stunned to discover comparatively very few. I found shots associated with Government using a new Celtics Crimson Sox plus hat, however, not anything else. The revolutionary You are able to Situations records in which Ruben McCain typically wears lids to protect their skin on the sunlight, even though photograph together with the account showed them using just what exactly usually any limitation with an American a flag.

"There will be code" by renlewei

Tue, 20 Sep 2011 04:21:23 -0500

Gucci Shoulder Bags Gucci Clutches http://www.saleguccinewbags.com/gucci-boston-bags-c-58.html">Gucci Boston Bags Gucci Messenger Bags authentic discount gucci bags authentic discounted gucci bags

"There will be code" by cheap baseball hats

Sat, 17 Sep 2011 03:52:28 -0500

I am sure to all the commenters here! http://www.capshoponline.com/

"There will be code" by [url=http://www.cheaphatsale.com/][url]Wholesale New Era Hats[/b][/url]

Fri, 09 Sep 2011 23:03:06 -0500

thanks for your sharing,it’s intersting, i will be your first victor.last time

"There will be code" by Henry Jack

Mon, 08 Aug 2011 19:32:45 -0500

There is but one step from the sublime to the ridiculous. new york yankees hats and caps fitted caps cheap

"There will be code" by San Diego DUI Attorney

Fri, 05 Aug 2011 09:05:31 -0500

I am pretty much amazed of the article content. I learned a lot from the interesting topics that are being discussed. It’s my pleasure to visit and learned things and facts of this page. I will be visiting this site more often for I am very intrigue with the topic that indeed catches my interest.

"There will be code" by okey oyunu oyna

Wed, 27 Apr 2011 13:43:48 -0500

nice.

internette görüntülü olarak okey oyunu oyna, gerçek kisilerle tanis, turnuva heyecanini yasa.

"There will be code" by SEO Firm India

Fri, 18 Mar 2011 13:32:44 -0500

It looks like you have really placed a lot of effort into your blog and I require more of these on the web these days. My husband actually loved your article. I don’t have a great deal to say in retort, I only this minute wanted to comment to say well done.

"There will be code" by Criminal Records

Thu, 17 Feb 2011 17:04:00 -0600

Not that they should have, but after half a century of development, shouldnt we expect standard interfaces for the most common applications instead of a set of guidelines, best practices and de-facto standards?

"There will be code" by Tenant Screening

Thu, 17 Feb 2011 15:14:20 -0600

Some of the topics you touched on resonate with me, and these views also seem to be in synchronism with Dewar and Shonberg’s article (hope the link posts properly) that I found very much matching how I think about the state of the software world today.

"There will be code" by smart card

Mon, 31 Jan 2011 14:02:24 -0600

This makes perfect sense, code is the building blocks of the web, I don’t see that going anywhere, anytime soon.

"There will be code" by Criminal Check

Thu, 27 Jan 2011 17:24:21 -0600

So, for the foreseeable future I think software will remain the art of crafting code to meet the requirements of our customers.

"There will be code" by iPad ePub Transfer for Mac

Fri, 21 Jan 2011 21:05:36 -0600

I really like this essay. Thank you for writing it so seriously. I want to recommend it for my friends strongly. An Professional transfer that can transfer the ePub books onto your iPad on Mac and export the iPad ePub to Mac local folder.

"There will be code" by http://www.blacktowhiteiphone4.com

Thu, 23 Dec 2010 00:20:44 -0600

now supplying the latest white iphone 4 conversion kit to make your iphone 4 different from others. As a fashion fans like you will surely love it.

"There will be code" by iPhone to Mac Transfer

Fri, 03 Dec 2010 07:30:39 -0600

I don’t know much about this topic. So, I am looking a way to solve it. I want to study. When I come to here, I think I am in the right place. the web gives me a lot of infomation, it is very informative. I think lots of people can learn much here. I will come to here again. Thanks.

"There will be code" by ipad video converter

Mon, 19 Apr 2010 00:29:38 -0500

you can read it also you can have a ty

"There will be code" by Kooba Handbags

Thu, 01 Apr 2010 01:11:29 -0500

Living without an aim is like sailing without a compass. with a new http://www.handbags4buy.com/ idea is a crank until the idea succeeds.

"There will be code" by v

Wed, 25 Mar 2009 07:19:38 -0500

I doubt the professionalism will emerge, though. Taking the saw/power saw analogy a bit further, you could imagine the “coding” industry move along from the garages (individual machines) to large manufacturing units (software companies with 1000s of programmers) where the level of professionalism would presumably increase multiple-fold similar to the manufacturing industry.

But we do have large software companies and not as much professionalism, nor is there perceivable change across the spectrum (in fact, smaller shops might have a better grip on professionalism, but i digress). The standard excuse given is a version of the “human body is finite and can be figured out, but the mind is limitless, thus no standard need apply”. There are no cookie cutters in this industry. The “software ICs” that were talked about in the 80s have still not arrived. Not that they should have, but after half a century of development, shouldnt we expect standard interfaces for the most common applications instead of a set of guidelines, best practices and de-facto standards?

It seems to me, therfore, that not only will there always be code, but also that there always will be more and more of it. How do we explain to outsiders (most of whom are our clients) our penchant for reinventing (or renaming) things over and over? Take for example RPC: we’ve gone through Unix RPC, Sockets, CORBA, RMI, and many more. And yet the defining thought behind these are the same.

While its required and behoves us as practitioners to call out the deficiencies of something like MDA, what is the way (or ways) to better code?

How do we become doctors from the barbers and healers that we are now? We certainly have the critical mass, but lack the will. Is something like the certified software professional the way? I’m not too sure.

I have two suggestions though:

Come up with a peer reviewed definition of what it means to be a software professional – using ietf style BoF meetings or unconferences or some such informal yet workable format – anything that would result in the average developer saying: “yeah, that makes sense to me”. it worked for building the internet, why shouldnt it work to build our careers and industry?
If we cannot standardise the mind, can we not look for patterns in what the mind has produced and standardise that? We have a ton of software that’s already produced. What’s stopping us from doing a cyc-style large scale project to analyse this and derive the standard patterns (or anti-patterns) and provide this as input to the rules that we use write code in the future (And here I mean something at least an order of magnitude more insightful and higher-level than our current crop of checkstyle, findbugs, etc)?

"There will be code" by v

Wed, 25 Mar 2009 07:17:53 -0500

While its required and behoves us as practitioners to call out the deficiencies of something like MDA, what is the way (or ways) to better code?

I have two suggestions though:

Come up with a peer reviewed definition of what it means to be a software professional – using ietf style BoF meetings or unconferences or some such informal yet workable format – anything that would result in the average developer saying: “yeah, that makes sense to me”. it worked for building the internet, why shouldnt it work to build our careers and industry?
If we cannot standardise the mind, can we not look for patterns in what the mind has produced and standardise that? We have a ton of software that’s already produced. What’s stopping us from doing a cyc-style large scale project to analyse this and derive the standard patterns (or anti-patterns) and provide this as input to the rules that we use write code in the future (And here I mean something at least an order of magnitude more insightful and higher-level than our current crop of checkstyle, findbugs, etc)?

"There will be code" by Marc

Wed, 25 Mar 2009 00:41:22 -0500

“There were no standards, no common rituals or behaviors, no common disciplines. If you got sick you might go to a barber, or a healer.”

And there is a reason there will continue to be custom solutions requiring custom skill sets and experiences. The body is finite, it can be figured out. However, not every business rule or chunk of business logic will work for everyone. We aren’t just programmers, we are problem solvers as well, thats half of it.

You may be able to standardize on the process one goes through to solving a problem…there are best practices for that. But definitely not in the implementation.

"There will be code" by Ken

Wed, 25 Mar 2009 00:26:27 -0500

I think it’s safe to say that basically every language in common use today is at least an order of magnitude better than Fortran in 1959. That was FORTRAN II, which did not yet have boolean logic, or a non-arithmetic IF statement. They had just added support for subroutines!

Even today’s Lisp is drastically better than 1959’s Lisp: that would have been LISP 1, which I believe didn’t have hardware numeric types yet (only Church numerals).

That’s not to say that software has kept pace with hardware, because it clearly has not. But if we’d really made virtually no progress in 50 years, then many of us would still be using 1959’s languages. Some of us still use Lisp because we find its abstraction-building capabilities still unparalleled, but we’re not using Lisp 1.

"There will be code" by Ravi Venkataraman

Thu, 04 Sep 2008 19:15:47 -0500

Twelve orders of magnitude? Some of the stated advantgaes are not really additive or multiplicative. If the volume of the hardware decreases by a factor of 1000, how does it affect my program? If the power consumption decreases by a factor of 1000, how does it affect my program? As long as the data can be stored in a reasonable volume of space, and as long as the power consumption is affordable, these factors don’t matter at all.

The fact that almost everyone can afford to compute does not mean that we’ll write programs that are “x” orders of magnitude better than the ones we wrote earlier. Writing programs is still a human endeavour.

It is like saying that because CPUs are 1000 times faster and we have 1000 times as much RAM, our cars should run 1000000 times as fast as they did!

Programming is still a human activity, as you pointed out. Unless we start thinking 1000 times as fast, and increase our memory a thousand-fold, we should not expect programs to be several orders of magnitude “better”, whatever “better” means.

As for AI’s writing programs, I believe that there is work being done on genetic algorithms, etc., that may lead to it. One only has to know about the chess playing programs of today that are better than the strongest grandmaster to realize that in the not too distant future computers will be able to “think” and make decisions, and write programs.

For now, though, the human rules!

"There will be code" by Simon Kirk

Sun, 31 Aug 2008 11:04:54 -0500

What an interesting analogy between medicine and software development.

Thinking about it a little deeper, I think the reason why Software has this lack of professionalism problem is both a blessing and a curse: accessibility.

In medicine, the accessibility is fairly limited: sooner or later there’s a limit to how many people can be involved, lopping off one another’s limbs, blood letting, etc.

But in Software, anybody with a computer can have a go.

I think that accessibility must be maintained, just as the professionalism must also come to be. The ability for anybody who wishes to create something wonderful is part of what gives Software its beauty: the limit is only the imagination of the programmer(s), and those without knowledge of boundaries often transcend them. Professionalism mustn’t stifle that creativity.

I hope that Agile will provide the links of craftsmanship that allows creativity to bloom while keeping chaos at bay.