i have code for 25 years, most of the days 16 hours per day

since opus 4.5 i have not written a single line of code, 50 days to date.

i did a ralph loop and exhausted my weekly limit in a day, then i had to code
without llm, turns out i forgot the map[k]v syntax for go, had to google `golang
map`.

i have been writing go every single day for like 10 years, it took 50 days of
not writing code to forget syntax i have been using hundreds of times per day.

you can ask, who cares what is the map syntax? its one in c, another in java,
another go.. a map is a map, its important to know the abstract concept.

machine code programmers were upset that assembly mnemonics made them forget,
assembly programmers were upset C made them forget, C programmers were upset
python made them forget, and now, i am upset opus made me forget.

perhaps forget is not the right word, the distance between you and the
electricity increases at each step, like woodworkers understanding wood but not
physics. and now ikea worker assembling a table not understanding wood.

a program is funciton of the programmer, how you code is how you think. that is
why it is really difficult, even after 60 years, for multiple people to work on
the same codebase, over the years we have made all kinds of rules and processess
so that code written by one person can be understood and changed by another.

it is as if you make a universe with your laws of motion. you model the emergent
dynamics of how information changes itself in and through your program; a world
of your own.

how important is the intimate relationship between the abstract and the real for
you to make a world you enjoy, the best world you can make?

some say its a split between those who love to build, and those who love to
code, code must solve a problem, it is nothing by itself, and this is true, just
as a wooden table has to solve a problem, but the question here is, how to make
a table you are proud of? that does not bend in the sun and snow? why do tables
even bend?

https://www.youtube.com/c/theprimeagen recently got one of the new commodore64s
and is now learning basic, and you can see every day, he is 20% better than the
day before. i miss that feeling. now every day i feel i am getting further away.
he is getting closer to the machine on its own terms. he is telling it what to do.

for reference, commdore basic is just intense:

```
10 rem cbm basic v2 example
20 rem comment with keywords: for, data
30 dim a$(20)
35 rem the typical space efficient form of leaving spaces out:
40 fort=0to15:poke646,t:printchr$(18)"     ";:next:rem 18=revers on
45 rem in the "if" statement, "then" can be omitted if goto or on goto is used
47 rem checking chr$(0) will not wait for a keypress, using "" instead
50 geta$:ifa$=""goto40:rem no ":" allowed before the goto
55 rem it is legal to omit the closing " on line end
60 printchr$(23):print"bye...
65 rem 23=white
70 rem end is not needed. the rem is a dummy so that line 70 is entered 
rem
```

you have a world model about how things work, e.g you can pull something with a
rope, but you cant push it with a rope. this is obvious to you, you know where
things are weak, how levers work, without even thinking. as you have grown into
this world you observe observe and model it in your head, you can simulate it
and predict what will happen next, even though you did not create it, nor you
fully understand it.

in the same time, thowe who understand the laws of motion, can use the world
better, for example to build a bridge, or a car, or go to space.

remember, in the end, types are erased, and only electricity exists. the
question is, how much electricity you need to understand to make a good world.