Articulating the ineffable. Programming language theory 
cognitive psychology. PhD @Stanford
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
A debugger is not a debugger, it is an interactive program executor. The sooner we internalize this, the sooner we can talk about what should really be considered a “debugger.”
A person debugging a program is a debugger. They use many tools to understand program behavior, such as an interactive program executor or program state displayer (printf). Which raises the question — how useful is interactive execution to understanding behavior?
Or differently: what other kinds of tools help debug / understand programs? Whyline showed that another framing is *automatic reduction of context*. Tools that can interactively eliminate regions of code unrelated to the bug. (Good idea, let’s do more of that!)
Exactly. You have to start from the perspective of the user. That's how innovation happens.
But what if the user doesn't know what they want?
Folks who design chips use a hardware description language (HDL) that can be complied into transistors. But before that happens, the HDL code runs through millions of hours of tests in a simulator. We need an analogous "software description language" model for programming.
A “programming language”? 
Conversely, the programmer is the bugger. Or maybe the enbugger.
And eventually the rebugger.
A true debugger should send you a notification after you’ve been staring at a problem for a long time: “You realize, don’t you, that you are getting exactly what you asked for, although it may not be what you wanted.” Whoa. Does that mean my mother was a debugger?
True. you are the debugger, not the tools you'd use for that.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
