Home > Uncategorized > Has the seed that gets software development out of the stone-age been sown?

Has the seed that gets software development out of the stone-age been sown?

A big puzzle for archaeologists is why stone age culture lasted as long as it did (from approximately 2.5 millions years ago until the start of the copper age around 6.3 thousand years ago). Given the range of innovation rates seen in various cultures through-out human history a much shorter stone age is to be expected. A recent paper proposes that low population density is what maintained the stone age status quo; there was not enough contact between different hunter gather groups for widespread take up of innovations. Life was tough and the viable lifetime of individual groups of people may not have been long enough for them to be likely to pass on innovations (either their own on ones encountered through contact with other groups).

Software development is often done by small groups that don’t communicate with other groups and regularly die out (well there is a high turn-over, with many of the more experienced people moving on to non-software roles). There are sufficient parallels between hunter gathers and software developers to suggest both were/are kept in a stone age for the same reason, lack of a method that enables people to obtain information about innovations and how worthwhile these might be within a given environment.

A huge barrier to the development of better software development practices is the almost complete lack of significant quantities of reliable empirical data that can be used to judge whether a claimed innovation is really worthwhile. Companies rarely make their detailed fault databases and product development history public; who wants to risk negative publicity and law suits just so academics have some data to work with.

At the start of this decade public source code repositories like SourceForge and public software fault repositories like Bugzilla started to spring up. These repositories contain a huge amount of information about the characteristics of the software development process. Questions that can be asked of this data include: what are common patterns of development and which ones result in fewer faults, how does software evolve and how well do the techniques used to manage it work.

Empirical software engineering researchers are now setting up repositories, like Promise, containing the raw data from their analysis of Open Source (and some closed source) projects. By making this raw data available they are reducing the effort needed by other researchers to investigate their own alternative ideas (I have just started a book on empirical software engineering using the R statistical language that uses examples based on this raw data).

One of the side effects of Open Source development could be the creation of software development practices that have been shown to be better (including showing that some existing practices make things worse). The source of these practices not being what the software developers themselves do or how they do it, but the footsteps they have left behind in the sand.

  1. TemporalBeing
    December 27th, 2010 at 18:35 | #1

    While I would suggest that historians have simply got their timeline wrong (that’s a different discussion), software often has the corporate culture issue – no sharing with others – which hinders software more than anything else. Software thrives on being shared, and being developed by communities of people; yet, most companies want to keep it under lock and key – understandable from how they view investments, but it makes software a lot harder to deal with.

    That said, I think there is still a considerable amount of maturing to be done by the software community, with all too many developers refusing to do things (e.g. coding style) inline with company/project policies (in the name of art), and obfuscating things (in the name of job security – which it isn’t) that they should not.

    This would likely be resolved more by separating the teaching of software development into two fundamental disciplines – engineering, which great amounts of structure/etc for the work place, and science, for academic research. All too much today software is only studied as science in unrealistic environments where students are taught that tomorrows computers will always be better than today’s so just do whatever you like and to hell with requirements.

  1. No trackbacks yet.

A question to answer *