This is my first attempt at a blog meme. With any luck my friends will get me off to a good start by helping me catapult the propaganda. Some may object that it’s off topic. Perhaps, although one of my reasons for being an anagorist is the market’s tendency to turn vocation-finding into a trial-and-error exercise. This meme is an exercise in assessing my strong and weak suits and maybe even coming up with an effective (if belated) strategy for dealing with that particular Reality.
The gist of the meme is to list three things in the course of your lifelong learning that came as natural as falling off a log, especially if they strike you as possessing elegance, expository power, arousal of curiosity, or best of all, a lot of formerly disparate concepts somehow “fall into place.” The other list is three things that are utterly opaque to your mind, that you have made repeated attempts to learn, but for some reason or other, you just don’t seem to be meant to learn these things.
Three things that make things make sense to me
- Taylor’s theorem
This is typically part of the second semester Calculus curriculum. This tied a lot of things together for me. Having already learned that polynomials are the easiest functions to differentiate/integrate, it comes as a relief to find out that all analytical functions are polynomials.
Stands for “Structured Query Language.” It’s the language at the heart of most relational database software. For me, at least, it has the gentlest learning curve of all the computer languages. Granted, that’s comparing a data definition language to programming language, but from what I’ve seen since then of the former, the designation still stands. The relational model is the way that I (without knowing it) always organized facts inside my skull. Taking a database course and encountering SQL gave me the easy means to communicate a lot of what I had been thinking for a long time.
- double entry bookkeeping
I never took a course in this. I encountered this idea because one day out of boredom I took a peek inside an accounting textbook. I was dumbfounded by the elegance. This is how you implement a relational database when you don’t have computer technology.
Three things that I simply don’t grok
The NIPA (national income and product account) of macroeconomics bears superficial resemblance to the balance sheet of accounting. But the appeal in that was the relational integrity; the way all the reports are derived entirely from the information in the journals. Macroeconomics would make sense as reverse engineering, but instead is a compendium of official statistics. Macroeconomics reads like alphabet soup to me. Its definitions of terms are wordy, and 90% disclaimers by weight. Try as I might, I simply can’t wrap my head around macroeconomics.
While generally competent at math, this particular branch of math eludes me. Sure, I can do cookbook statistics, but even that I have to look up because I can’t remember the formulas or the procedures. An intuitive understanding of significance tests and the like completely eludes me.
- object oriented programming
While I find it elegant to call methods on predefined objects such as columns or rows or whatever of an Excel worksheet with Visual Basic, the class definitions involved in writing object oriented programs from scratch is something I could never find the patience for. It just seems like you have to write many many lines of code just setting things up before you can write code that does things. I can see the advantages of object oriented programming for group projects, but never having managed to break into the profession, my only opportunities to program are whatever projects I take up for my own amusement, and they seem to be small enough to be less hassle without object oriented rubrics.