4 ms·

> " tolerance for repetition that characterize her condition are also pretty much a recipe for success in ... computer science" Obviously, the author knows not

• Johngibb 14y ago
  I know where you're coming from, but I'd like to present a counterpoint based on a potential misunderstanding. On the one hand, repetition expressed as writing the same code over and over again smells of poor engineering. Abstraction, code reuse, refactoring - all and productive means to avoid repetition. I don't think that's what's the parent meant though. There IS a lot of secondary repetition in our field in terms of sitting at same desks every day, working long term on the same project, fixing similar types of. Ifs, responding to emails erc. Basically, the auxiliary facets that are required to be a good coder but don't directly involve coding are pretty repetitious. Don't get me wrong - there are alternatives for some of these, working from home, better productivity tools, better management etc. but my experience in this career after 5 years leads me to believe there is a somewhat intrinsic aspect of repetition. To me, it's lot as assume, because as You were pointing out that good code doesn't involve repetition and I agree and am ok with it because of that.
• robryan 14y ago
  It makes sense in a research context, where there is going to be a lot of repetition with small differences before you hit on a real improvement to current methods.