Emergent Coding
Emergent Coding is a decentralised computer programming paradigm applying the theory of emergence in order to achieve practical developer specialisation. A developer applying emergent coding can contribute to a project without revealing their intellectual property thus preserving prospects for repeat business and obviating any need for licenses, goodwill, obfuscation, or DRM style mechanisms.[1]
Overview[edit]
In 1968 at the first of the NATO Software Engineering Conferences, Professor Douglas McIlroy first suggested that software development would be inhibited and ultimately plateau until the process was automated and industrialised.[2] This theory was later formalised and in 1976 published by McIlroy as the academic paper “Mass-Produced Software Components, Software Engineering Concepts and Techniques”.[3][4] While it is easy for a developer to specialize with McIlroy's approach, it is virtually impossible for a developer to build a viable business as a specialist. Emergent coding harnesses the theory of emergence to achieve practical developer specialisation.
With emergent coding, developers contribute features to a project, and leave the project binary to emerge as the higher-order complexity of their collective effort. Typically, developers “contribute” their feature by causing smaller features to be contributed by peers, who in turn do likewise. By mapping features to smaller features delivered by these peers, developers ensure their feature is delivered to the project without themselves making a direct code contribution.[5][6][7][8]
Peer connections established by these mappings serve to both incrementally extend a temporary project “scaffold” and defer the need to render a feature as a code contribution. At the periphery of the scaffold, features are so simple they can be rendered as a binary fragment with these binary fragments concatenated back along the scaffold to emerge as the project binary.[9][10]
Emergent Coding can be viewed as ‘turning the compiler inside-out’ and incorporating developers ‘into’ the compiler itself, obviating the need for High-level programming languages, Libraries, Application programming interfaces or a codebase.[11][12]
References[edit]
- ↑ "A reflexive exploration of two qualitative data coding techniques". uair.arizona.
- ↑ "NATO Software Engineering Conference 1968". homepages.cs.ncl.ac.uk. Retrieved 2019-07-29.
- ↑ M. D. McIlroy, “Mass-Produced Software Components, Software Engineering Concepts and Techniques (1968 NATO Conference on Software Engineering),” Van Nostrand Reinhold, New York, 1976.
- ↑ From the text of an address he gave to DLSLUG on 12 March 2009.
- ↑ Bitcoin Cash City Conference (5 Sep 2019). "An Emergent Economy for Software Design - Mark Fabbro".
- ↑ Randolph, Justus J. (2008). Multidisciplinary Methods in Educational Technology Research and Development. HAMK Press/Justus Randolph. ISBN 9789517844567. Search this book on
- ↑ ICSE 2018 (30 May 2018). "Live from ICSE: Industry Forum - Noel Lovisa".
- ↑ "A PEER-TO-PEER SOFTWARE ENGINEERING SYSTEM" (PDF).
- ↑ Bitcoin Cash City Conference (5 Sep 2019). "Bitcoin Cash App Exploration - Dr. Saad Butt, Ethan Cannon and Dao Zhou".
- ↑ NewsWatch (10 June 2016). "Code Valley - Innovative Software Engineering - NewsWatch Review".
- ↑ Medium (14 Sep 2019). "What is Emergent Coding? - Jonald Fyookball".
- ↑ "Code Valley - Industrializing The Software Industry". www.superbcrew.com.
This article "Emergent Coding" is from Wikipedia. The list of its authors can be seen in its historical and/or the page Edithistory:Emergent Coding. Articles copied from Draft Namespace on Wikipedia could be seen on the Draft Namespace of Wikipedia and not main one.
