Blind Finishes

I finished a programming task. It was a long time since I had to work with substantial pieces of code, juggling components together, bug testing to see if everything worked out, writing excessive number of comments ( a good program has more words than code after all),

…and I have no idea if it is right.

When completing assignments, normally one ought to have the confidence to know whether or not a task is finished. Usually, this would come from a “correct-looking answer”, a solid rationale, or self-confidence. However, none of this comes to mind here. The answers look correct, but may be off. The rationale is correct, but it might not be correct to someone else’s checklist. Self-confidence, like plants, do not grow under the shade of the institution.

And so, this comment for this week is that, although work has been completed, there is no knowledge on whether or not it’s even good — and that might be the most important thing ever. When there is no reference point to define what is good or not, the one thing that will be certain is a kind of confusion, but that is okay. In the end, it is not whether or not someone else says you completed a task that means you did, it is you who sets the definition of completion. That is the subjective power that an institution cannot take control of.