I am still :ablobcatsweatsip: ing on Nostr: trying to create a specific definition of a programmer's 'mental model' of code and ...

trying to create a specific definition of a programmer's 'mental model' of code and trying to boil it down to the most axiomatic questions possible.

So far I have:
- if I need a change in how something behaves, where would I go to change that?
- how does the program behavior change if I change this variable.

Off the top of my head these two things cover most things a programmer does, including bug fixing. It covers the forward and reverse case (seeing a program behavior and finding code vs seeing code and predicting change in program behavior).

What else am I missing?