3 ms·
The best part of this list is that with some tweaks, the commandments can pretty much apply to any field of personal and professional pursuit. One rule I might
by danso 12y ago
The best part of this list is that with some tweaks, the commandments can pretty much apply to any field of personal and professional pursuit.
One rule I might add (and one that is also easy to apply elsewhere): Remember that far more time will be spent reading your code than writing it.
Grokking this not only has practical implications for how you write code (suddenly, the importance of style guides becomes clearer), but it makes you realize that this is how projects get built: programmers re-using libraries that contain encapsulated, clear functionality. Realizing that someone has to read your code -- even if that someone is mostly just you -- requires a modicum of empathy...and more often than not, this aids in the design process.
A common complaint about learning via something like Codecademy is that you might learn the syntax and how to solve problems...but you don't get much guidance on how to apply that knowledge to real projects. I think part of this is because with Codecademy, you're only writing code for the auto-checker to compile and test. Once you start writing code for humans to comprehend and re-use, it becomes easier to see how code becomes a real-world project.