News for hackers. Stuff that matters.
Re:Signs that you're a bad programmer by dionidium on Friday August 07, 2009 @02:58AM (#747188)
Sometimes the (seemingly) simple act of trying to come up with a name for a subroutine helps me reason about what it is I'm trying to do (whether the chunk is re-usable or not).
Re:Signs that you're a bad programmer by scott_s on Friday August 07, 2009 @11:21AM (#747707)
Not being able to think of a good name for a variable, function, class or data structure is a show-stopper for me. If I can't come up with a short, descriptive name, then I assume I don't really understand what I want that thing to do or be. I'll sit and think until I'm satisfied I have both a meaningful name and a grasp on how this thing fits into the problem.
Re:Signs that you're a bad programmer by kevindication on Friday August 07, 2009 @08:50AM (#747478)
I don't know if you've tried this, but if you write down some pseudocode before you really get started, the logical chunks of the program will take their names straight from the pseudocode.
Re:Signs that you're a bad programmer by jamesbritt on Friday August 07, 2009 @11:35AM (#747745)
Or do comment-driven development: write the comments for the method first, then convert the (hopefully!) plain English into code, ideally so that no comment is needed.