at the end coders are gods over the turing maschine: writing code is 'having power', coding is 'to speak the magic language'. this magic words are than reality executed by the slave machine (or an error).

in the 80ies on homecomputers young people could step into this world of 'power' of interaction. the 16/32 bit homecomputer even brought the mouse, the gui, a lot of colors, memory, modern fast cpus and were modern as hell (and not so expensive like the mac). a whole game could be made on one computer from sound, to graphics, to code.

your code controls a machine (with assembler) and over this all the the output and all the interactions. so computers became our funslave, they do what we 'want' - a quite strange thing. so for a lot of coders: coding is absolute power (over a small maschine) and explains also why they till today want to control everything. they want to write their own engines and not use a game engine.

coding is defining rules, creating your own world defined by this rules and there is also the link to games. games at the end are also defined by rules and are creating a magic circle (huizinga). so creating videogames is at the end double coding: you create computer codes for game codes.

starting with basic, gfa-basic, c and than assembler (bbs demo) on atari st imp89 1988+

switching to mac os. coding in c++ 1995+

java-codings in applets (not documented here) 1996+

flash-codings(?)

switching to mac os x. coding in objective c & opengl 2002+

codings: c# & unity and-or.ch &&& 2005+

homebrew-c-codings for nds (look at and-or.ch) 2006+

assembler-coding (6502) on atari 2600 2014: axe

assembler-coding (6802) on vectrex 2015+: vecZ & a demo

// plato-tutor-script-coding more here: turings assembly line and-or.ch 2020

not mentioned here torque, unreal and co.