wip test simulation

chapters/00. Coding Contingencies.md

@@ -176,7 +176,7 @@ Notes:
 
 ---
 
-then we need to combine thigs from the three categories
+Now we need to combine thigs from the three categories.
 
 -   developer, cobol, work
 -   sailor, assembly, survival
@@ -186,7 +186,7 @@ then we need to combine thigs from the three categories
 -   class, python, publishing
 -   engineer, python, art
 -   artist, red stone, writing
--   student, red stone, modding
+-   hacker, red stone, modding
 -   engineer, red stone, research
 
 ## ITERATE
@@ -269,15 +269,66 @@ Notes:
 
 ---
 
-**DISCLAIMER:** old writings, this was a random combination. now the approach is to generate combinations starting from references.
+Now that the setup is done, the simulation can start.
 
-now that the setup is done, the simulation can start.
+To build something meaningful out of these initial combinations we can balance between what is defined and what is not.
+Leveraging on the unknown of the simulation gives room for narrations.
 
-to build something meaningful out of these random combinations we can balance between what is defined and what is not.
+<!-- does it make sense to specify the moment ? -->
-leveraging on the unknown of the simulation gives room for narrations.
 
-so for example we have #04
+### Developer, cobol, work
 
+00
+
+-   Developer
+-   Cobol
+-   Work
+
+01
+
+-   North american, white, young, self-taught programmer
+-   A business-oriented language, with an english-like syntax designed to be self-documenting and highly readable.
+-   an open position in a national retailing chain, for developer with experience working on mainframes.
+
+02
+
+-   Program readability was a commendable design goal, and ahead of its time. But how did it come about that the main emphasis was on readability by managers, instead of readability by programmers?
+-   Was there any evidence at the time that managers wanted to read programs?
+-   Did the COBOL committee seriously believe that the users could not handle grade school operators of `+`, `-` , `x`, `/`?
+-   (Sannet, 1981)
+
+-   Has never written a line in COBOL.
+-   Ready to accept the challenge in order to get the opportunity to get closer to the mainframe.
+-   It sounds like the certification of being a real developer™️.
+
+-   The company's processing center is on the ninth floor of a large department store.
+-   An harshly lit room.
+-   Women —all Filippinas— it seems, are working heads down, at keypunch machine.
+-   Red flag: data entry with keypunch instead of computer system at a terminal?
+-   Data entry systems change, bad habits and exploitment don't.
+-   [Workers Leaving the Googleplex](http://www.andrewnormanwilson.com/WorkersGoogleplex.html), 2011
+
+03
+
+-   Haunted by the fear of getting caught as being stupid. Coming to a new system and not knowing how to log-on. Lie low and learn the basics.
+-
+-
+
+04
+
+### Sailor, assembly, survival
+
+-   sailor, assembly, survival
+-   teacher, lisp, business
+-   artist, javascript, accessibility
+-   designer, javascript, publishing
+-   class, python, publishing
+-   engineer, python, art
+-   artist, red stone, writing
+-   hacker, red stone, modding
+-   engineer, red stone, research
+
+<!--
 ```
 
 a musician what is their background?
@@ -306,6 +357,7 @@ which particular aspect of pure data resonates with their view of the world?
 is it the open source nature and the licensing of the source code?
 the welcoming community thriving around the programming language?
 or the visual paradigm that facilitates the thinking about and connecting abstractions together?
+-->
 
 ## INSERT DOCUMENTATION AS ELEMENT
 

chapters/materials.md

@@ -0,0 +1,42 @@
+# Materials
+
+Here a collection of excerpts that could be useful at some point.
+
+## Documentation, from Early History of COBOL
+
+Dumentation was handled fairly informally, in the sense that there were no requirements in the early development for what could or should be documented. In particular, there was no record kept of the reasons behind certain decisions, except insofar as individuals might have these in their hand notes.
+
+At the September 17, 1959, meeting there was a considerable discussion as to what the first public description should have as its objective.
+Even at that time there was a considerable discussion of the difference between the language manual issued in the name of CODASYL and the individual manuals that would be
+issued by each manufacturer.
+
+(The Early History of COBOL, Jean E. Sammet)
+
+## Intended Purpose & Users, from Early History of COBOL
+
+It was certainly intended (and expected) that the language could be used by novice programmers and read by the management. We felt the readability by management could and would be achieved because of the intended use of English, which was a fundamental conclusion from the May 1959 Pentagon meeting.
+
+Surprisingly, although we wanted the language to be easy to use, particularly for nonprofessional programmers, we did not really give much thought to ensuring that the language Would be easy to learn; most of our concentration was on making it "easy to read" although we never provided any criteria or tests for readability.
+
+COBOL was intended for use only in the United States, even though experience from Grace Hopper's group had shown that the transliteration into another natural language at this level was trivial. I believe that subsequently other countries (e.g., Germany, Japan, Netherlands, and Sweden - but not France) have used COBOL with English key words but their own data names.
+
+What this does to their readability is left to the imagination!
+
+## Pressure for COBOL everywhere from the Dep of Def
+
+do you think
+C O B O L would have survived without the pressure applied by the Department o f Defense
+in requiring C O B O L on all m a c h i n e s ?
+
+hylarius copypaste from OCR pdf
+
+## comments in COBOL
+
+MARCOTTY: F r o m Paul Abrahams: " W h a t thought was given to c o m m e n t s in C O B O L ?
+Why a r e n ' t they allowed in the Data Division?"
+SAMMET: We didn't think they were needed in the Data Division.
+
+## Math operators in COBOL
+
+Did the COBOL committee seriously believe that the users could not handle grade
+school operators of `+`, `-` , `x`, `/`?