From the article, I recognize that the author is differentiating programming, that is to me "coding" from all the other activities in the software development lifecycle, as he mentions in his third paragraph. I assume that many of you also recognize this, but that some might not. I bring this up because in replying back to the point of the article and whether or not we "know how we program" it is important to define what we mean by programming and what boundaries we place in the activity "programming" which is different than the activity "design" or the activity "testing."