A Message to the Future
Linda Rising
MAYBE iT’S BECAUSE MOST OF THEM ARE SMART PEOPLE, but in all the years I’ve taught and worked side by side with programmers, it seems that most of them thought that since the problems they were struggling with were difficult, the solutions should be just as difficult for everyone (maybe even for themselves a few months after the code was written) to understand and maintain.
I remember one incident with Joe, a student in my data structures class, who had to come in to show me what he’d written. “Betcha can’t guess what it does!” he crowed.
“You’re right,” I agreed, without spending too much time on his example and wondering how to get an important message across. “I’m sure you’ve been working hard on this. I wonder, though, if you haven’t forgotten something important. Say, Joe, don’t you have a younger brother?”
“Yep. Sure do! Phil! He’s in your Intro class. He’s learning to program, too!” Joe announced proudly.
“That’s great,” I replied. “I wonder if he could read this code.”
“No way!” said Joe. “This is hard stuff!”
“Just suppose,” I suggested, “that this was real, working code, and that in a few years, Phil was hired to make a maintenance update. What have you done for him?” Joe just stared at me, blinking. “We know that Phil is really smart, right?”
??116 97 Things Every Programmer Should Know
?
???????????????Joe nodded. “And I hate to say it, but I’m pretty smart, too!” Joe grinned. “So if I can’t easily understand what you’ve done here and your very smart younger brother will likely puzzle over this, what does that mean about what you’ve written?” Joe looked at his code a little differently, it seemed to me. “How about this,” I suggested in my best “I’m your friendly mentor” voice, “Think of every line of code you write as a message for someone in the future—someone who might be your younger brother. Pretend you’re explaining to this smart person how to solve this tough problem.
“Is this what you’d like to imagine? That the smart programmer in the future would see your code and say, ‘Wow! This is great! I can understand perfectly what’s been done here and I’m amazed at what an elegant—no, wait—what a beautiful piece of code this is. I’m going to show the other folks on my team. This is a masterpiece!’
“Joe, do you think you can write code that solves this difficult problem but will be so beautiful it will sing? Yes, just like a haunting melody. I think that anyone who can come up with the very difficult solution you have here could also write something beautiful. Hmm…I wonder if I should start grading on beauty? What do you think, Joe?”
Joe picked up his work and looked at me, a little smile creeping across his face. “I got it, prof, I’m off to make the world better for Phil. Thanks.”