Talk:Erlang programming techniques: Difference between revisions
Jump to navigation
Jump to search
imported>Howard C. Berkowitz (New page: {{subpages}}) |
imported>Howard C. Berkowitz (→Implications on Software Engineering: new section) |
||
| Line 1: | Line 1: | ||
{{subpages}} | {{subpages}} | ||
== 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 [[User:Howard C. Berkowitz|Howard C. Berkowitz]] 23:52, 8 May 2009 (UTC)) | |||
Revision as of 17:52, 8 May 2009
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))