Make it correct, clear, concise, and fast; in that order

“Make it correct, make it clear, make it concise, make it fast. In that order.”

– Wes Dyer

This is a great quote for new coders. I think every teacher can think of a student that is way to fixated on writing fast code.

But that leads to two problems with newbie coders. Well, probably more than two. But two come to mind.

First, they might spend so much time trying to make the code perfect that they’re never actually able to get a working algorithm. And that’s something that can carry over once they leave the classroom. Code that solves a problem is better than fast code that doesn’t, and way better than fast code that doesn’t even run.

And two, often really efficient code isn’t intuitive to look at. Sure, they might understand what they wrote when it’s turned in. But what about a few weeks or months later? Would their peers be able to look at the code and immediately tell what it’s doing?

Now, I’m not suggesting that students shouldn’t work towards writing efficient code. It’s just that maybe it shouldn’t always be the first priority.

Why ClassCube?

Are you spending too much time grading your students' source code?

ClassCube is an online tool for Computer Science teachers that allows you to create lab assignments for your students. They'll submit their code online and ClassCube will automatically grade it for you.

Teaching with ClassCube…

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes:

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>