I had no idea what I was doing , but it worked and it broke the path for me . Documentation can kill this . If I can go and look up all the little pieces , and loosely put them together , I no longer am looking at code .
When the narrator starts working on the code , how can he be described ?
- He 's going to give up .
 - He knows what he is doing .
 - None of the above choices .
 - He is clueless .


He is clueless .