Talk:Erlang programming techniques

Citable Version ^[?]

To learn how to update the categories for this article, see here. To update categories, edit the metadata template.

Definition: The philosophy and the most powerful programming techniques in Erlang (programming language). [d] [e]

Checklist and Archives

Workgroup category: Computers [Please add or review categories]
Talk Archive: none	English language variant: American English

Unused subpages
Unused subpages: - Bibliography - External Links - Works - Discography - Filmography - Catalogs - Timelines - Gallery - Audio - Video - Code - Tutorials - Student Level - Signed Articles - Function - Addendum - Debate Guide - Advanced - Recipes - Citable Version

Implications on Software Engineering

Open question: should this be a separate article?

The Erlang Programming Techniques presented here has some implications for not only how Erlang programs look, but also for the software engineering disciplines used to create a system.

list: more value-adding code (Jan Henry Nyström's work with Motorola), aggressive coding style which gives higher productivity (ref: 4x article + ? ), hot code upgrade (enables more agile approach to software releases), documentation : functionality and error handling separated, ...

(copied from original article page without change Howard C. Berkowitz 23:52, 8 May 2009 (UTC))

Talk:Erlang programming techniques

Implications on Software Engineering

Navigation menu

Search