Since when has dithering over details been recognized as a favorable trait in programmers? Also, that response was in the context of intro-level CS courses: so if you're fretting over the implementation details of glorified Hello World applications, instead of focusing on the overarching concepts , I'd be inclined to say you'd better change your ways or you won't be a very good programmer.
1. Not every CS graduate will work as a programmer. Many will work in other technical roles within the industry. Do not assume that CS knowledge is only appliable to programming. I graduated from a CS course and I'm currently a sysadmin, and having a CS degree makes me a better professional;
2. Having little interest in the details is usually just common-speak for lack of technical skill. Having the skill/competence and lacking the interest is seldom found in the same person;
3. It's the introductory classes that lay out the ways in which one faces every programming problem. Not paying attention to detail means allowing bad habits to root themselves. I still remember some of those "details" from my introductory classes to programming 12 years ago, and I frequently other people (otherwise experienced) commiting mistakes that I manage to avoid due to those "details".
Better to have an overall view while learning to program, and a penchant for details when implementing one tiny little part of a 1 million line code base that 100 other people are also working on.
Not stating a fact, just pointing out that in the context of a technical profession, that citation actually sounds derogatory.