This pad text is synchronized as you type, so that everyone viewing this page sees the same text.
To prevent this pad from appearing in the etherdump, paste (or leave) the following code:
. Warning: DirtyDB is used. This is fine for testing but not recommended for production. -- To suppress these warning messages change suppressErrorsInPadText to true in your settings.json BECOMING SOFTWARE
Some boundaries that appear to be fuzzy when we try to define them (appeared wed. // thurs.): - fuzzy line between data and software - fuzzy line between software and hardware - tollerance to noise, software being less tollerant to changes. That was something that could define software from data. - fuzzy line between software and signal (signal vs. noise) - machine learning algorithm and the training data, adaptibility - developer/ - forking (when does one software becomes another software?) - Is a social network a piece of software? - FPGAs and Hardware Definition Languages
(FRIDAY) - labor (is trainining an ML machine labor? "the reCATCHPA insight") - process (Agile practices) "using" your users to define the requirements of the product (features in the product become defined by the feedback of the release cycle) - services and agile processes collapsing the divide between production and use - Agile methodologies collapse product, labor and process. - there is also the pain and labor that users bring to software that is rarely documented (e.g., activists using Signal)
- comment based on a study of floss chat tools (secure messaging?)