Talk:Erlang programming techniques: Difference between revisions

From Citizendium
Jump to navigation Jump to search
imported>Howard C. Berkowitz
(New page: {{subpages}})
 
imported>Torben Hoffmann
(→‎CZ clean-up: new section)
 
(One intermediate revision by one other user not shown)
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))
== CZ clean-up ==
To Howard: thanks for the nice editing.
I tried to fill out the Definition subpage, but it did not link right, so now we have a Erlang+programming+techniques/Definition page in addition to the correct page that works in the [[Erlang programming language/Related articles]] topic.
Is there a way to delete the wrong version?
[[User:Torben Hoffmann|Torben Hoffmann]] 08:45, 12 May 2009 (UTC)

Latest revision as of 03:45, 12 May 2009

This article is developing and not approved.
Main Article
Discussion
Related Articles  [?]
Bibliography  [?]
External Links  [?]
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

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))

CZ clean-up

To Howard: thanks for the nice editing.

I tried to fill out the Definition subpage, but it did not link right, so now we have a Erlang+programming+techniques/Definition page in addition to the correct page that works in the Erlang programming language/Related articles topic.

Is there a way to delete the wrong version?

Torben Hoffmann 08:45, 12 May 2009 (UTC)