work week is finally over. time to over this long (US) weekend
Any conversation
signals. thinking about shifting my mental framework to identify signals instead of waiting for concepts to be assembled. exploring the amount of energy and opportunities for distractions through the operations of processing what just happened and what is happening to short circuit latent and unnecessary systems. cut through the assembly processes and identify the raw signals. recognizing that naming these "raw signals" is misleading. maybe, shifting observability lower in the stack.
I'm doing experiments with short attention-span students and code. Starting with python, and, oddly, now working in BASIC. As a C programmer of 40+ years, I find this aesthetically and pedagogically displeasing, but I am delighted to see them getting fully absorbed in writing
130 PRINT "You have been eaten by a bear!" : GOTO 900. Yes there is spaghetti, but it's their spaghetti and they seem to take delight in debugging it. Python will come later. Good morning, techno.
Konstantin Scharf - Still Moving
my wife is concerned that my job search will not be fruitful due to my use of ai to build and orchestrate my json and latex resume and cover letter build pipeline. it has not changed much since I initially built it almost 20 years ago. there are only so many ways that the core metadata can be assembled for presentation, yes?

