Isn't this simply a description of your "thought clearing process"?
You think in English... not Ruby. I'd actually hazard a guess and say that really, you think in a semi-verbal semi-phyiscal pattern language, and not very well formed one, either. This is the case for most people. This is why you have to write hard problems down... you have to bake them into physical form so you can process them again and again, slowly developing what you mean into a shape. Julian On 09/05/2012, at 2:20 AM, Jarek Rzeszótko wrote: > Example: I have been programming in Ruby for 7 years now, for 5 years > professionally, and yet when I face a really difficult problem the best way > still turns out to be to write out a basic outline of the overall algorithm > in pseudo-code. It might be a personal thing, but for me there are just too > many irrelevant details to keep in mind when trying to solve a complex > problem using a programming language right from the start. I cannot think of > classes, method names, arguments etc. until I get a basic idea of how the > given computation should work like on a very high level (and with the > low-level details staying "fuzzy"). I know there are people who feel the same > way, there was an interesting essay from Paul Graham followed by a very > interesting comment on MetaFilter about this:
_______________________________________________ fonc mailing list fonc@vpri.org http://vpri.org/mailman/listinfo/fonc
