Software life cycle in Erlang

Tom Whitcomb thomaswhitcomb@REDACTED
Thu Jan 26 22:34:31 CET 2006

I find that erlang is extremely well suited to an iterative,incremental (XP) development model.  

Focus on delivering business valuable stories in short iterations using the practices of TDD, refactoring and YAGNI 

Yes, erlang's functional orientation makes TDD very effective, but the all important neccessity of "refactoring the code base" across iterations is made cleaner and easier by erlang's declarative nature and simplifying capabilities provided via pattern matching, message passing and high-level language constructs.    

Erlang aligns well with the basic iterative development practives and just plain makes development easier, more productive and more fun.

Erlang rocks and there is a great story for using Erlang and XP!


"Francesco Cesarini (Erlang Consulting)" <francesco@REDACTED> wrote:

>The correct link (I promise, we are getting rid of the frames soon!!) to the Test Driven Development thesis is
>TDD proved to be the best approach.
>>-----Original Message-----
>>From: Martin Carlson [mailto:martin@REDACTED]
>>Sent: Thursday, January 26, 2006 12:14 PM
>>To: erlang-questions@REDACTED
>>Subject: Re: Software life cycle in Erlang
>>I would say it hate to do with the preconditions, is there a spec (the 
>>optimistic approach..)? in that case what kind of spec you got, what 
>>are the requirements, are there any high risk requirements and so on.
>>In any case an iterative model is proven to be very flexible 
>>productive. Have a look at Fowlers page, lots of info.
>>Some pointers though:
>>General agile stuff:
>>Martin Carlson
>>On Jan 25, 2006, at 3:19 PM, Thomas Lindgren wrote:
>>> --- "Eduardo Figoli (INS)" <eduardo@REDACTED>
>>> wrote:
>>>> I'm trying to figure out the best model for software
>>>> development in Erlang.
>>> The best _model_ seems to be iterative development of
>>> some sort, perhaps test driven. AXD 301 had great
>>> success with steadily improving "increments", to take
>>> one of the great success stories.
>>> Taking a number like 35% for implementation means your
>>> whole project is done about 50% faster (in 2/3 the
>>> time) even if the language permits infinitely faster
>>> development than the state of the art, simply because
>>> the rest of the phases aren't concerned with
>>> programming. (That's the usual argument against
>>> switching programming languages, of course.) This
>>> doesn't seem right -- the added flexibility also means
>>> you can use powerful new development processes.
>>> My recommendation: try to "switch to better rules".
>>> Best,
>>> Thomas
>>> __________________________________________________
>>> Do You Yahoo!?
>>> Tired of spam? Yahoo! Mail has the best spam protection around

Switch to Netscape Internet Service.
As low as $9.95 a month -- Sign up today at

Netscape. Just the Net You Need.

New! Netscape Toolbar for Internet Explorer
Search from anywhere on the Web and block those annoying pop-ups.
Download now at

More information about the erlang-questions mailing list