Scarcity, Prestige, and Function

On some reflection while studying for the CFA, there's something quite wrong with the programming and software design culture at where I'm working in at NUS RMI. Well, maybe it's not that there's anything wrong with it, but that it doesn't even exist.

Programmers and hackers (outside of mathematics) don't seem to exist there. The problem, of course, is that the work there is perceptibly deeply involved with software engineering.

Because of this, it seems like I enjoy a little more prestige than the average intern (although, still being an intern, that prestige is non-material). However, I can only justify it as being the one-eyed-man among the blind. Too many mistakes in architectural design, too much trial and error, too many inappropriate problem definitions. It's slowing down my work.

As a saying goes, out of sight, out of mind. An organization without expertise in an area wouldn't consider its importance.

The source of prestige, scarcity, compromises function.

Taking CFA a mistake

CFA is on Sunday, today is Wednesday. It is usually at times like these, within reach of a goal, when I ponder and reconsider the goal.

In hindsight, registering for the CFA and taking it so soon is a mistake. Elaborations after the exam. Luckily, even if I skip or fail it due to reallocation of efforts, the opportunity cost is only 1500 SGD (never taking it again) or 600 SGD (retaking it at a later time).

Why did I register for it? Probably an insufficient and incomplete decision framework at the time of choice. Seems like I've grown wiser, wise enough to refute my past decisions with the confidence of reason.