In the past few weeks, we’ve started a lot of things that we haven’t finished. We’re working through a few books at once — Python for Kids and Super Scratch Programming Adventure. We have an unfinished game of Zork on the iPad with the thief still skulking around. We started Dash online and worked our way through a few lessons; and now that tab is staring at me while I write this, guilting me as if it can see that the Snap Circuits are out on the dining room table and I have a post-it note reminding me to order a Raspberry Pi. Lego sets are half built, we have dice but no game in progress, and a solar robot with no sun (or perhaps just a bad panel).
Don’t even get me started on apps. The Room is still unsolved, Can You Escape is holding me hostage, and I can’t remember the last time we watched a whole video with Khan Academy.
Sometimes I feel as if there is too much out there; too many cool opportunities, too many cool projects: just too many parts and books and sets that pile up, covering the surfaces of my house and making me feel very very anxious over how many things we’ve started but haven’t finished.
I mean, don’t we need to finish them? Like library books? Or… dinner?
I’ve been internally debating whether it’s better to go wide or go deep when it comes to Geekery. Is it better to dabble, trying dozens of games and books and projects? Or is it better to seriously commit to one thing — Python, let’s say — and immerse ourselves in it fully?
Because the kids have limited time. Very limited time, once we toss in school and homework and language lessons and sports. And I want them to discover all the things I thought were fun as a child, and experience all the new stuff that has come out in the meantime. Some of the activities will fall to the wayside out of disinterest, and I think that’s okay. They shouldn’t keep up with something if it doesn’t speak to them. But that still leaves too many interesting possibilities to fit into a compact schedule.
It’s important for a child to follow a project through to its end point. To decide to code a video game, and finish the video game so there is the pride that comes from having a finished product. But how many finished products are enough finished products? The Wolvog completed a great game at computer camp last summer. Can we count that as a goal reached and now play around for the rest of the year?
I think more than other areas of life — at least for girls — there is a feeling that if a chosen area isn’t explored well and deeply, the cry of “fake geek” will ring out, as the Doubleclicks express so well. I’d love to expose my kids to facets of Geekery that I don’t know well, such as Dungeons and Dragons. It’s been over 20 years… uh… maybe more… since I’ve last played. And unfortunately, it’s a game where it’s hard to find friendliness unless you go deep. Unless you fully immerse yourself in that world and learn the rules and commit to a campaign. I can’t speak to what it is like to try to fit in as a boy, but I can tell you what my daughter will experience if she doesn’t delve deeper than the Ring trilogy and the Hobbit when it comes to Tolkien; her thoughts will be dismissed, her commentary written off. Even if she does read the Silmarillion or The Children of Húrin, her ideas still may be dismissed due to her sex. But at least she can fight back by shooting off all the names of Morwen.
And then there is just the bare fact of not going deep enough: you can’t, for instance, accomplish a lot with a surface understanding of coding. Is it worth touching on programming at all if we’re not going to follow through to the point where we can depart from the books and do our own projects? Sometimes depth matters beyond proving your Geek mettle.
With writing, there are some ideas that fully come to fruition, gently guided from a series of notes into a published novel. There are many other ideas that grabbed me in the moment, filled me with excitement while I wrote, but fizzled out after a chapter or two. It’s not that I didn’t love those stories, but it wasn’t the right time to tell them, either due to mood or timing or other commitments. I know there is always a chance that I’ll circle back to those stories, especially if the right opportunity presents itself.
Maybe that’s the attitude I need to take with some of our projects. That it is better at times to go wide until you find the place to go deep. And plumbing the depths of a bit of Geekery isn’t something that happens for every project, book, or game started, but instead is something that can’t be always planned or predicted. Sometimes we just stick with things because they stick with us.
Or sometimes your mother tells you that she spent a lot of money on that Lego set, and it better get built.
Do you think it’s better to go wide and try a lot of things, or go deep with just a few areas of Geekery?