Yesterday, my twenty-year-old asked me if I had time to proof the work report he had prepared for a university co-op course. He had been working at a prominent mobile apps company, helping make cool things happen on iPhones and other such devices for the past eight months. Since he had kept us fairly up to date as to what his projects involved, I figured I knew enough to have a go at the paper.
Delusional mother.
There comes a point in life when your children know far more than you will ever know. I suspect that this moment passed for me a long time ago, but because I happen to have fairly tactful children who would never rub in this sort of thing, I had been largely oblivious to this fact until yesterday.
I sat down at my computer and confidently opened the report file. I began to read. I sort of understood the title. Sort of.
“Developing Cross-Platform Mobile Economy Software.”
Not entirely sure about the “Mobile Economy” part but I figured I would forge ahead and sort it out by context, the way intelligent people approach challenging reading.
It got murkier.
There were several references to C++. This was, coincidentally, the grade I was feeling that I would be lucky to achieve as a proofreader on this assignment.
There was mention of Android. Well, since seeing Star Wars in 1976, I associate this term with alien robots: more or less how I was beginning to view the people who would understand the paper my son had written. (But excluding my son, of course, because I love him and would never casually lump him in with your average bunch of alien robots.)
Following the Android references, there was a fair bit of talk about “bindings,” which I only understand in the context of ski equipment. No skis were mentioned although things were definitely going downhill for me at this point.
I did understand the prominent word, “code,” although I can’t feel too triumphant about that; I only recognized it as being the explanation for why I couldn’t understand this report one iota—it was obviously written in CODE. Duh.
Halfway through the paper, I was glad to see the word “Java”; at this juncture, I was more than ready for a large cup myself. Taking a break to put the coffee on, I pondered the term, “deadlock,” which had just surfaced. This, I was pretty sure, described my current relationship with this report.
I got my coffee and I persevered, proofing to the end as best I could, with all the good intentions of a diligent mom wanting to help out her kid. I’m pretty sure I corrected some dicey punctuation, and I did remove the forbidden passive voice here and there, but I fear my contribution was extremely limited.
I guess it’s just the way of evolution that this kind of thing should happen. It’s a weird feeling, though, to somehow pass the torch to your offspring (or realize they picked it up when you weren’t looking) and be left watching and wondering just how far they’ll run with it.
No matter where they end up, I know I’ll be somewhere in the distance cheering them on.