A discussion of how to do Computer Science well, particularly writing code and architecting program solutions.
Showing posts with label guidelines. Show all posts
Showing posts with label guidelines. Show all posts
Wednesday, July 24, 2013
Repost: There's nothing like a tidy codebase
When I grade student assignments, around 90% of the grade is for what the code does. The other 10% is for how it looks, because There's nothing like a tidy codebase. So take some additional time and help ensure that the code you write is readable.
Tuesday, April 3, 2012
Rules of Computer Science
As I've spent these many years learning and practicing computer science, I've come to have a couple of "rules" (i.e. guidelines) of programming.
1) If a computer can execute something, you can write it in C. (aka Turing-completeness)
1a) Still, it is probably faster to write the program in a high-level language.
2) The computer does what it is told to do. There is no magic.
2a) If a behavior is not what you expect, then you don't know what you told the computer to do.
I am sure there are other such "rules", so please share if you have other maxims from your time and experience.
1) If a computer can execute something, you can write it in C. (aka Turing-completeness)
1a) Still, it is probably faster to write the program in a high-level language.
2) The computer does what it is told to do. There is no magic.
2a) If a behavior is not what you expect, then you don't know what you told the computer to do.
I am sure there are other such "rules", so please share if you have other maxims from your time and experience.
Subscribe to:
Posts (Atom)