Michele Pasin / Quotes

Code Architecture

The source code of prompt_toolkit should be readable, concise and efficient. We prefer short functions focusing each on one task and for which the input and output types are clearly specified. We mostly prefer composition over inheritance, because inheritance can result in too much functionality in the same object. We prefer immutable objects where possible (objects don't change after initialisation). Reusability is important. We absolutely refrain from having a changing global state, it should be possible to have multiple independent instances of the same code in the same process. The architecture should be layered: the lower levels operate on primitive operations and data structures giving -- when correctly combined -- all the possible flexibility

Saved 22 March 2018 / github.com ↗

#code #objects #source-code

Code as a medium for improvisation

Programming language source code underlies almost all digital technology. The emerging practice of Live Coding brings source code from technical craft to live…

Live Notation: Transforming Matters Of Performance #code #source-code #live-coding #digital-technologies #idea

A program is not its code, process or algorithm

we agree with Irmak that we cannot identify a program either with a code, a process, or an algorithm. The reason is that this view conflicts with common…

Towards An Ontology Of Software: A Requirements Engineering Perspective #code #algorithm #same-algorithm #program

A rigorous foundation for version numbers

By identifying the rationale for these changes in the different abstraction layers, our work contributes to establish a rigorous foundation for software…

Towards An Ontology Of Software: A Requirements Engineering Perspective #abstraction-layer #software #code

Code is not necessarily an artifact

In the light of these observations, a code is not necessarily an artifact. If we acci- dentally delete a line of code, the result might still be a computer…

Towards An Ontology Of Software: A Requirements Engineering Perspective #code #artifacts #computer-program #program #computer-code

Different codes, same algorithm

A code implements an algorithm. Following Irmak [8], we take here an algorithm to mean a pattern of instructions, i.e. an abstract entity, a sort of process…

Towards An Ontology Of Software: A Requirements Engineering Perspective #algorithm #code #same-algorithm #execution

Feasibility prototypes

These are written by engineers in order to address technical risks during product discovery before we decide whether something is feasible or not. Sometimes…

Flavors Of Prototypes #developers #algorithm #code