Hockey and Honing The Craft

I did not ever think I would grow up to describe myself as a hockey player. I remember being alright at “getting the ball away” when playing floor hockey as a youngster. Some of the kids who knew things about hockey were angry that I never passed it to anyone, and they had every right to be. I was just flinging the ball as far away as I could.

I can also remember getting my two upper front teeth knocked in while playing floor hockey during Grade 11 or 12. One of them is porcelain now, and the root on the other fortunately survived. Thankfully there’s no gaps! From that day on until a few months ago, I pretty well stayed out of sports’ way.

Fast forward to today: I’m feeling a bit down on myself at work because I haven’t found the level of productivity I aspire to. Two particular kinds of decisions come up occasionally, and my annoying default response is to freeze up and find a distraction. If it’s a particularly tough little knot to figure out, I can burn a lot of time thinking, getting frustrated, finding something else to do, returning and reloading the mental context, then getting frustrated and removing myself again in a sort of loop.

This has got me thinking — just a bit — about the dreaded topic of “whether I should even be doing this kind of work at all”. In many other situations, I feel I can act quickly and land on my feet, but these ones just catch me. The first is the “should I write it one way or another” moment, and the second is far worse: “I wrote it the one way, but now I see the problems with it are bigger than I guessed… should I continue down this road despite the looming clouds, or undo my progress and try the other path? Maybe there is a third option that hasn’t occurred to me yet?” That one kills me. Especially when the “looming clouds” are something that appears time consuming, might still fail, and I don’t really know how to do it.

So anyway, back to hockey. It’s floor hockey, by the way — I’m not awesome enough to do this on skates yet — tonight I got a goal and a half, while playing defense. The first goal, the full goal, was a lucky shot that soared in under the crossbar. Felt great. I played a pretty solid game (for me) tonight: kept on people, cleared the ball to the right places, stopped lots of incoming attacks, and I didn’t get as out-of-breath as I have in the past.

I’ve only been doing this once a week for two or three months. When I started, I was dying by half-time, and I noticed very clearly how bad I was. It was still fun, but I felt like I was as much harm as good out there. That feeling kept on for a while, but it’s been less and less. I’ve made steady progress. But wait: I didn’t tell you about my other goal yet.

They got one on us, and we were already down by a few. It felt like we kept outsmarting and outplaying them, but something would slip and the ball would fly just perfectly off of legs or a mask into the net. A fluke of flukes! I felt angry — not at the other players, but at how we just couldn’t catch a break. The goalie passed me the ball and I started to bring it up; the other team moved in to block me as I got to half, and my teammates broke over the halfway, but were pretty well covered.

I focused my anger, and decided to be tricky! I deked right like I was going to pass while I ran left, bringing the ball with me. I dodged around a confused-looking forward, ran toward the net, halted the ball and shuffled it away from a nearby defense, then shot! It went straight past the goalie, who just stood there dumbfounded. Everything had lined up perfectly: I felt like a boss. While triumphantly strutting back to the other side, I heard shouts: “doesn’t count! doesn’t count!”

Why the hell doesn’t it count? Were you guys subbing really slowly? That’s your fault.

No, actually, see, there’s this rule in hockey. When the goalie passes it to a person after a goal, that person can bring it forward with them up to half, but must pass it over the line. I didn’t pass the ball: I just ran with it. The rule probably exists because rushing the net like that gives an advantage. The reason everyone just let me past is because they all know the rules, and I looked like an idiot. A complete amateur, which is what I am.

At the end of the game, they decided to count it anyway. We lost by a wide margin regardless, and they were feeling charitable. I made a complete beginner’s mistake tonight, but that doesn’t change that I played a solid game. I poured my heart into something, and it was a dumb idea. But I learned something.

My stuff at work? I’m probably making stupid decisions all the time. As long as I keep my head level and really work hard, I’ll learn. The same goes for every thing in my life: I have mistakes ahead of me, and should consider them as welcome opportunities to learn from. All I can do is try to be better each day.

Electrogravitics?

So, this is a pretty wacky wikipedia article. I wish that the uncertain pseudoscience-y nature of it weren’t quite so uncertain, because then it would either be a “wow neat!” or just not be worth writing about. The article talks about things called “lifters”, which utilize an effect known as an “ion wind”, where charged particles are actually pulled between electrodes due to their charge difference to cause lift. This means that these devices wouldn’t work in a vacuum, and are relatively useless.

But the way the article is written has just enough bait there to make you wonder about this other, crazier explanation being involved. Not as a replacement for ion wind (which is a very real thing), but as an additional effect under the right circumstances. Mythbusters apparently tried to replicate this myth and busted it by showing no lift generated by one of these machines in a vacuum, but the conditions described for the “mysterious effect” to come into play sound very demanding. Dense piezoelectric crystals and incredibly high voltages being pulsed at particular frequencies. This has the earmarks of crappy science: a holy-grail like claim and a billion reasons to explain why the failed tests that falsify the claim aren’t really conclusive.

But then there’s also all this military stuff. The article has a claim that there was a demonstration to the military in the 1950s showing off the mysterious effect, and that the whole thing was immediately classified and spawned 40-50 US military projects lasting over 20 years. The guy who performed the demonstration worked for the military and the precursor to Lockheed Martin and apparently on a secret project in France, and his job through all of this was to “research antigravity propulsion”. So, if it’s just ion wind, were they all just not well enough informed for those 20 years? But then, all of those projects were shut down in the early 70s by a policy intended to get rid of crap that wasn’t helping the military.

And then you read that the guy who reported on this “mysterious force” being shown off is a science fiction writer and model rocketry enthusiast, and start thinking that he could have just fudged some facts. But what isn’t disputed is that a demonstration did take place by a real man whose name is attached to the general ion wind effect, Thomas Townsend Brown, and that he did in fact work and research gravity propulsion systems for the next 20 years, while a large number of military projects surrounding the concepts were going on.

It’s back and forth, back and forth. Each extra bit of research turns up something very legitimate looking, which ends up being the most ridiculous thing yet. These videos (make sure you listen to the music a bit) are where I called it quits due to an outbreak of hysterical laughter. And yet, if they didn’t have the weird music and “gravitec” logo everywhere, they would have seemed to be doing something really credible. It’s kind of like when a spammer sends you a really well crafted, personal-looking email with a spoofed address, but opens with “Dear Sir (Madam) ,” and blows the whole operation.

While reading up on this, I was reminded of (and ran across) things in the same wishy-washy region. Burkhard Heim and Heim Theory and the Hoverbike and the Moller Sky Car. They’d all be so cool, if they were more than just zany nonsense.

Our Noble Defense

Collected Data

Yesterday, a blogger wrote about a topic dear to the hearts of many programmers. The community at large came together to shout about it, and the spectacle has been a pleasure to watch. I’ve collected what (qualitative) data I can, in the hopes of distilling useful things.

The original post, by Jeff Atwood:

Some of the flood of responses:

..and I’ve certainly missed some. (each (hn) link leads to the hackernews submission/discussion for that article)

A Brief Summary of Atwood’s article, list form:

  • Atwood is annoyed by the “learn to code” craze
  • he jokes? about why the mayor of new york might want to learn
  • Suggests that coding is like plumbing; not vital know-how for everyone
  • Agrees that a little bit of programming could be useful
  • Ends by saying that basic computer skills, how the internet works, curiosity, reading, and interpersonal communication skills are ultimately more important

Typical response formats / focuses:

  • Comments on the flaws or virtues of the overall premise
  • Attack (or applaud) Jeff’s choice of analogy (plumbing)
  • Attack Jeff’s equation of “knowing how to code” to “knowing functions, pointers, and recursion”
  • Clarify the distinction between “coding” and “programming” in this context
  • Tell an anecdote about programming being useful to non-coders (lots of these)
  • Tell an anecdote about non-coders doing harm by programming (fewer of these)
  • Interpret “What Jeff Really Meant”
  • Express anger at the post’s obviously-bait title
  • Zed Shaw being brash and over-the-top
  • People naively thinking that replying to Zed will minimize that problem
  • People pointing out misconceptions or errors raised in other people’s responses

Analysis

This article is eerily well crafted for virality. I wish I could credit Jeff with adding minor logical foibles like non-sequiturs, hasty generalizations and strawmen on purpose. Or subtly drawing a brand new distinction between synonyms, then using that distinction to appear to call for war while actually calling for supper. It super-effectively gets under people’s skin and drives them to want to respond, but they’re unlikely to disagree on the whole. Unfortunately, to actually give that credit feels like breaking Hanlon’s razor. Cock-up before conspiracy: these are probably just errors.

Jeff clearly has a good sense for how to deliver a topic to be read and talked about, because here we are, but his suggestion for people to learn to communicate effectively felt … hypocritical in its conext. Much of the surrounding discussion has been a consequence of misunderstandings of his post, and most responses are in fact along the same lines as the points Jeff makes.

After hours of reading, I will join the throng of interpreters and attempt to reflect the collected opinion of the masses, imperfect lense that I am:

“People shouldn’t plan to dive into this field and come out overnight as experts, making hot social app startups or being paid top dollar for their skills, nor should people encourage others to dive into it for those reasons.

But it would probably be good for people who aren’t career-programmers to learn a bit about how computers work, and how to automate simple stuff, and if they’re curious after that, they should keep at it. Oh, and people should still learn other stuff, too.”

I feel that this adequately sums up the spirit of Atwood’s original post. I also feel that this is pretty much a representative average of what has been said in response, back and forth, for the past 12-20 hours.

Action Items

I’m reminded that many programmers sense something special and important about our discipline. Some responses glazed over the distinction between programming itself and the virtue it brings, but it is clear that people perceive some mix of problem solving, recognizing cause and effect, strategic thought, comfort with trial and error, raw utility, and more in the writing of programs.

I think that what they’re feeling is related to what Harold Abelson spoke about in the first SICP lecture, that we’re just beginning to learn to “formalize notions about process” as Egyptian surveyors founding geometry (and all modern math) were just beginning to formalize notions about space. There’s something truly special, even magical here, and I think that people perceived Jeff Atwood’s post as an attack on the special nature that we sense. I believe that specialness is what so many people have really been defending.

My chief takeaway is to think about better ways to identify, express, and know that thing. Whatever it is. Before we finish, I’ve got to quote the SICP again. This time the opening quote:

“I think that it’s extraordinarily important that we in computer science keep fun in computing. When it started out, it was an awful lot of fun. Of course, the paying customers got shafted every now and then, and after a while we began to take their complaints seriously. We began to feel as if we really were responsible for the successful, error-free perfect use of these machines. I don’t think we are. I think we’re responsible for stretching them, setting them off in new directions, and keeping fun in the house. I hope the field of computer science never loses its sense of fun. Above all, I hope we don’t become missionaries. Don’t feel as if you’re Bible salesmen. The world has too many of those already. What you know about computing other people will learn. Don’t feel as if the key to successful computing is only in your hands. What’s in your hands, I think and hope, is intelligence: the ability to see the machine as more than when you were first led up to it, that you can make it more.”

Alan J. Perlis (April 1, 1922-February 7, 1990)

No matter how great we perceive the virtue of programming to be; even if we think of it as a literacy, Perlis has it right. Like reading, and like math, the best thing to do is to make it fun first, and then the knowledge will flow. If we become a bunch of missionaries, or Bible salesmen, I’m certain we’ll have lost the best part.

Day 8: Progress Report

Warning: bit of a boring show today — just plans and record keeping.

Learned, Keep, Start, Stop

I’ve completed one week of blogging each day. What have I learned, what should I keep doing, what should I start doing, and what should I stop doing?

I’ve Learned

  • Things may fall into place easily, or take a lot of effort. No pattern yet.
  • Starting after 10:00 PM means I won’t finish until after midnight.
  • My best posts have specific messages to deliver.
  • Cut things that don’t need to be said.

Keep

  • Blogging.
  • Trying to get exposure to topics which give me reasons to blog.
  • Thinking about the post earlier and earlier in the day.
  • Meticulously editing things. Thanks to Robyn for some inspiration here.

Start

  • Writing as soon as I start thinking.
  • Thinking earlier — days in advance, not hours in advance.
  • Trying not to let this mess up my bed time.
  • Learning so that I can explain, instead of learning for its own sake.

Stop

  • Worrying about correctness. I tend to be wrong anyway, so why work so hard at it?
  • Quitting on topics that I don’t feel like writing about at the moment.
  • Trying to trick myself into starting new focus items (things to do for 21 days) early.
  • Trying to accomplish too much, and thinking about what I haven’t accomplished.

Summary, or Commentary, or something

That’s all just sticks in the sand. I don’t (yet) have any metrics to base these on, so it’s just gut feelings for now. I’m pleased with the progress so far, and will definitely continue. I just need to find ways to integrate this into my day other than appending it to the end.

Next week I might try to write a plan of each post first, and I’d like to start researching a topic the day before writing about it. I’ve made some headway today — first draft written at 6:30 PM in a barber shop, third draft now at 11:01, and I’m mostly wound-down for sleep.

Thanks to the friends and family who have been reading and giving feedback. I appreciate it a ridiculous amount. Now it’s time for sleep, where I’m a viking.

On Learning Math (largely, ‘complaints on’)

I have been ‘planning to learn more math’ for longer than any person should. I’m going to try to outline the roadblocks I’ve run into, and we’ll see if some solutions fall into place. My bet is that the actual reason I haven’t learned much more math is that I haven’t really prioritized it, but who knows? Maybe it’s the world’s fault.

Tricky algebra leaps

I’m unable to find the original source, but I’ve read that a single unfamiliar word in a paragraph can seriously throw off a reader’s comprehension. (the closest thing I could find is this (pdf)). So, when a professor sets out to explain a concept from start to finish, care should be taken to ensure that each step in an explained process is clear and easy to follow — even at the expense of time or space.

Professors often seem to skip why and even jump past most of how to arrive at what a little sooner. I ran into an example of this today, watching the first video lecture offered by MIT for single variable calculus.

The professor poses a problem to the class about finding the area of a triangle made up of the x and y axes and a tangent line to a function. He explains the “calculus” part of the problem very well, but then seems to straddle showing the rest of the problem for completion’s sake and actually teaching us how to solve it.

At one point he needs to find the x-intercept. Rather than explain why it needs to be found and how to find it in concrete terms, he just starts pulling pieces of information from the last five minutes of work into an equation, while changing them slightly and performing transformations on the equation, often skipping multiple steps at a once to save time and space on the chalkboard. After doing all of it, he doesn’t stop and explain why this was done or how it worked — he just jumps into the next piece of the problem.

This is where it gets even worse: there is an opportunity to repeat the work to reinforce it, where the professor could even ask his students to tell him what to fill in and promote active learning, but he decides to be clever instead. Noticing that the function in the question is “y = 1/x”, he calls upon an “argument by symmetry”, and shows very thoroughly that “y = 1/x” means “yx = 1”, which means “x = 1/y”, so everything we just did to solve for the x-intercept can be done for the y-intercept by swapping x and y wherever they occur.

Don’t get me wrong here: that’s a cool logical tool, a cool pattern to show off, a good thing to teach, and this part is even well taught! He shows the trivial step in switching y = 1/x to x = 1/y — but the professor left considerably more complicated transformations unmentioned just seconds ago, and has essentially just said to the class “and what we just did (whether you get it or not), we do again.”

One could argue that the impetus is on the attendants of the lecture to ask for clarification. One could also argue that the bits of math which are unrelated to calculus aren’t worth focusing on in a calculus class, and anyone who is lost should do the remedial work required to get up to speed. It’s also hard for the professor to guess how low level to get. During my teaching experiences, I often felt like I was dragging things out and boring everyone to tears whenever I showed a full piece of code.

Video lectures make this less of an issue, thankfully. I watched the lecture at 2x speed, and rewatched the part of the lecture where the prof worked through the problem multiple times, pausing whenever he got ahead of my head. No single step was too complex, but all together it took some real thought to understand some of the less-trivial changes. It could just be my lack of experience and rustiness in this case, but it seems to be a common issue for teachers.

A dialogue with the class

Continuing that line of thought, I recently took lectures on set theory and proofs. I feel like I got very little out of the second half of the semester, which devolved into the professor writing for 4-5 minutes, turning to the class to say “as you can see, the axiom of choice applies” and turning back to write for 4-5 more minutes. This could happen multiple times in a row each class, sometimes just to solve a single problem.

This may sound like the flip of the instance above — being too low level, going too slowly, showing too much, but I should clarify: the steps being taken here were not all trivial. Often, new concepts and methods of argumentation were being introduced alongside manipulations and substitutions that went by without remark.

This may be an effective method for some people. Maybe it’s similar to what I ran into in my own classroom: the topic seems so obvious to the professor teaching it that it’s kind of like writing prose on the chalkboard. They expect us to just read and understand. Perhaps there’s a sense that “this is the way math is taught”, or a machismo idea of “if you can’t follow this, then you can’t don’t do math”. I’m not sure what the motivation is; I hope it is not something like those.

What I think would work best is a genuine dialogue with the class. Even if there’s 80 people in class, it seems to me that knowledge might be more effectively conveyed by an active exchange, perhaps begun by posing the problem in as non-technical a set of terms as possible, and inviting people’s ideas about how to solve it. When the super-geniuses in the front row respond with a series of symbols, the professor can nod and say “that’s great, but let’s try to put this into simple, every day language.”

From that point on, the regular people who actually need to be in the class have a chance of learning something. The professor can ask leading questions, and try to use real world concepts to provoke thought and inquiry from his students.

When they suggest an idea, it might lead down an interesting — maybe incorrect — path. She could work it out on the board, reiterating the motivations for what’s about to happen, and explaining how what she’s about to do next corresponds to what we just discussed. Again examples from the real world could be used to illustrate why a concept makes sense or doesn’t work as we’d expected. When people know why a thing is being done, it seems likelier that they’ll grok how it is being done. At the end, they’re also far likelier to understand what has been done.

While this sounds great to me, it might not engage anyone other than myself, or those I share a learning style with. It might be a complete failure of an idea that was tried before. Maybe this is what tutorials typically are. I didn’t get this experience in any of my classes, and I haven’t ever heard of math class being like this. It just feels intuitively like it would be a breath of fresh air.

Accumulation

Yet again, I can’t find the research I’m looking for — I think this one came up in a TED talk about khan academy; at the end Bill Gates comes onto stage and has some very awkwardly scripted dialogue with Sal Khan about the topic. Anyway, earlier in the video, Sal shows some of the metrics they had been testing out in grade school programs using khan academy for teaching. They found that some kids rocket through the lessons, while some others struggle, and he spoke a little about the implications of one of their findings on the idea of giftedness in schools.

The students who were struggling often failed to understand just a single aspect of a single lesson, at times because they had missed an even earlier piece of information that the lesson relied upon. Once armed with that single piece of information they needed, they would typically shoot forward and rejoin the students that at first glance had appeared to be gifted. The suggestion was that students that do the best may simply be the ones lucky enough not to have missed the most important parts of class.

This is one of the sticking points in my attempts to go back to learning math: I have no idea where to jump into it. Whenever I do, I either feel like I’m missing vital knowledge, or like I already know everything I’m being taught. It’s kind of like picking up a book that you were reading a year ago: pick a random spot and things seem familiar, almost boring, but some interspersed pieces seem entirely foreign. It’s tough to tell what’s been forgotten versus what hasn’t been read!

For example, I don’t know many trig identities, or projections and the like from discrete geometry in grade 12, but I tend to use radians and remember pieces of plane-intersection math. I also learned a fair bit of combinatorics, but can’t recall the definitions of Pick versus Choose. Say I go back to where I feel fully certain I know everything that’s going on: soh cah toa and simple polynomials from grade 10 — it seems like a mountain range of repeated knowledge to be braved before I could get back to real math.

Advice

Having put my thoughts down, reviewed and edited and shuffled them around so they’re neat and tidy, I feel like I’ve detected some things that would be neat to investigate about math education. Real world examples for higher level topics in math would be something excellent to write about (I know that this person has a few great examples for e and an introduction to calculus), but pages about spaces, and metrics, and lie groups, and multivariate calculus — it would be cool to read down to earth explanations of that stuff.

If you’re setting out to learn math (like I, presumably, am), I think it makes sense to have a target you want to hit. Something you want to be able to understand or accomplish. I don’t, though — that’s probably a problem. Too often, I just wander around aimlessly and feeling emptyhanded and emptyminded after a collection of skin-deep first encounters with topics I can’t begin to understand yet. If I chose a specific destination, it’d be a lot easier to find, draw, recognize, and even just to read a map. But good luck even finding a destination!

As a final note, the math I’m talking about in this post is, by and large, not the real math that mathematicians wish everyone knew about. I have read some of the Mathematician’s Lament (pdf), and agree with it as enthusiastically as a layperson justifiably may. Sadly, I know of no place to find better education, and I am not in school any longer. For now, I plan generally to bring myself up to the task of real mathematics, instead of trying to pull real mathematics down to a place where I can try it out.

If you can suggest to me a destination, a resource, or a way to pull real mathematics down from the stars and into reach, by all means, do so. I’d love to hear about it.