The author laments on the difficulty with teaching beginners, how to sound human, and the concept that translating one problem to another is the hardest thing in software.
Join the DZone community and get the full member experience.Join For Free
Whatever new awaits you, begin it here. In an entirely reimagined Jira.
On Monday I built Conway’s Game of Life in Google Docs. Prep work for a short talk given to the non-technical part of our team at Yup. It was supposed to make it fun and easy to show everyone how to make their own lives easier.
“Is this how you hack websites?” <- first question
Nope. Not easy.
Everyone loved the game of life. They grokked that complex patterns emerge from four simple rules. They could see the beauty in that. They loved the Wikipedia gifs of gliders and oscillators and other things people have built in Life.
“This is a boring game, man. Not only is it slow, but you’re playing it in a spreadsheet.”
That was a fair point. The lack of timers in gDocs does make the game tedious to play and not many people associate spreadsheets with fun. I’m sure they exist, I just haven’t met them yet.
Nobody grokked how implementing a silly game from 1970 translates to something practical. The conceptual leap from “You can manipulate cells to make patterns” to “You can automate common tasks” proved too hard.
I should have seen that coming.
Translating one problem to another is the hardest thing in software. Like, the hardest and most hardcorest of things. It took four years of hard computer science before somebody showed me how to formally prove that one problem is the same as another.
I expected everyone to get it the first time they saw some code. That was dumb.
Seeing the potential in a technique isn’t quite as hard as proving that two problems are the same, but it’s still hard. My whole life consists of:
- See problem
- Find 1 of N common patterns that solves it
- Adapt solution to problem
^ this is why experience matters ^
Most people’s lives don’t look like that. I should have used a tangible example and that would make the presentation better and also miss the core tenet of coding.
From that point onward, the presentation was a train wreck.
You say function, their eyes glaze over. Three people explain it. Each words it differently.
You say object, their eyes … you get the picture.
You say loop … yeah …
I never realized how much jargon programmers use. How much jargon I use in my own head! Concepts I don’t even realize are jargon. Can I even sound like a normal person anymore?
But people don’t think of objects as bags of methods and properties. Programmers do.
It was like culture shock from hell. We couldn’t even find a common language to speak in. The whole thing was a mess.
I didn’t teach anyone how to code who didn’t know how to code before my talk. I don’t even think I excited anyone about learning more. My presentation didn’t make anyone feel empowered.
At most, I managed to convince everyone that programming is an impenetrable arcane magic known only to a select few.
My job security is now safe. Perhaps too safe.
Published at DZone with permission of Swizec Teller , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.