Thoughts on “Crappy Coder Signs”
I was browsing my feeds in Google reader and came across this blog entitled “Signs You’re a Crappy Programmer (and don’t know it)”. For the most part I thought it was fairly accurate with the exception of not following the rule of trying to make your functions less than 20 (30/40/10/whatever) lines of code.
Now I’m not hardline on it, I think one should try to make all functions as short as they possibly can, but I do understand that some functions just can’t be made that way. I think preaching hard line either way is a bad plan but one as a general rule should try to keep functions short and sweet. Writing big long functions makes it hard for people besides yourself to follow the code quickly. I’ve dealt with my share of crappy functions that were a hundred lines long and totally unclear. Thats what you get when you work with people that aren’t programmers first though.