Things are in fact taken away. Code as a language doesn't tell you why it exists. It only describes a process, not the purpose of that process. And unless your

Things are in fact taken away. Code as a language doesn't tell you why it exists. It only describes a process, not the purpose of that process. And unless your programs are formally verified this process that you have codified most likely will not meet the requirements to satisfy the intended purpose. A typical non-technical "assignment" that's given before someone is fluent is to describe in excruciating detail/list of steps how to make a peanut butter and jelly sandwich. The point of the exercise is to show students that you need to remove all ambiguity. Or at least as much as possibly. What the exercise doesn't show is.. why are we making a list of steps to tell someone how to make a sandwich. “If you give me six lines written by the hand of the best debugging programmers, I will find something in them which will hang his operating system.”