Software development is a knowledge acquisition activity, not a manufacturing activity.
I frequently get asked why I write my own frameworks, my own blogging software, my own blogging client, even my own presentation software. That's the answer: knowledge acquisition.
A few thoughts. I find that I immediately doubt the credibility or seriousness of anything published with an AOL logo on it. What a brand problem.
Second, it seems that your response is a veiled refutation of John's premise that:
there are some people who just aren't good at finding prior solutions, or at understanding them once found, and they may contribute to unnecessary re-creation of software, increasing both cost and risk to larger projects. But they're not the norm
I really like the idea of programming as knowledge acquisition. But the bit about "unnecessary re-creation of software" seems to contradict his whole piece and smacks of a little elitism if you ask me.
Posted by Justin Watt on 2007-02-07
Posted by John Panzer on 2007-02-07
Posted by Nick Nolan on 2007-02-08
Posted by Mike Cantelon on 2007-02-08
Posted by Luke on 2007-02-09
I have argued this and frothed at the mouth, and thought I was the only one who saw this. Wrong, of course.
And, don't let anybody tell you it is for those who are learning. No! Learning never ends, and every time you write new code, you learn. Even if what you are learning is a new bug (or the lack of a feature) in your own programming language.
(Removed my address, because I think it may be reaped by bots - can it? Here, anyway, of you want it: revence27 at g m a i l dot com)
Posted by Revence 27 on 2007-02-10
Posted by Bill Higgins on 2007-02-06