What is the proper name for the bit of code that's currently being executed? I've suddenly realised that its a concept you think about constantly when coding, but its so much a part of the scenery so to speak that you never consciously consider it.
Edit: just realized I didn't really answer the question, I believe what your actually talking about is a statement.
I usually jump at the chance to talk about stuff from my old EE days :)
Currrent statement or active statement at the code level
I know that when I'm in the flow coding, there is a sort of Tick:the-program-does-this, Tock:the-program-does-that stepwise execution of the code in my head.
There are many answers as to what the hardware is actually doing with the instructions, but more generally what exactly is the name of an imaginary discrete state of a program that currently only exists in a coders head?
This is what I'm trying to get at. There isn't one is there? It's weird.
I would have used 'Cursor' or 'Program Cursor'. But I'm now convincing myself that that a database term.
An example that bites Haskell programmers are space leaks due to too much partial evaluation and not enough full evaluation. Other problems include keeping a file open for too long and leaking the fd. An ideal computer has infinite space and no files. A real one... nope :)
The advantage of functional programming languages is that you get to write part of your program as though you have an ideal lambda calculus evaluator. But at some point, you still have to realize that there's a grey box under your desk that doesn't know what a lambda or fixed point is. (But this is better than programming languages that say "hey, you've got a heap, a stack, and some registers! well, so long!")
My version:
OP's version: So the real test of a good programmer is one who can write a routine that crawls the source code of a bad programmer and tells them what they should really be doing.