When I read the title, I thought, "Hey, that sounds just like me." But after reading it, I realized that his use of "perfectionism" as an excuse is just incompl

When I read the title, I thought, "Hey, that sounds just like me." But after reading it, I realized that his use of "perfectionism" as an excuse is just incomplete. Perfectionism can explain underperformance, certainly. A perfectionist might write half of a timed essay, and the part that exists might be outstanding. But incomplete or slow is generally insufficient when it comes to a job. While he may suffer from a bit of perfectionism, that's not what holds him back; he's simply indecisive and using "Oh, I'm rewriting everything" as an excuse for his incompetence, uncertainty, or anxiety for solving the actual problems. "Rails vs. Node.js" is a contrived, invented problem. It's really easy to blame things on the language or framework when things are tough, but I think everyone does this to some extent; it's not a problem faced exclusively by perfectionists. Wise perfectionists understand that perfection is impossible. I think the best programmers, overall, are both pragmatic and perfectionistic. People just have to get over their overwhelming preference for one or the other and use both to their advantage.