"The programmers you'll be able to hire to work on a Java project won't be as smart as the ones you could get to work on a project written in Python. "
LMFAO......I busting my spleen!!!!!
I TOLD you guys to learn Python!!!!
No wonder Gadget is in a tizzy
"Good hackers insist on control. This is part of what makes them good hackers: when something's broken, they need to fix it. You want them to feel this way about the software they're writing for you. You shouldn't be surprised when they feel the same way about the operating system."
No - but you should tell them to STFU and use some of that "greatness" for the task at hand.
I do agree with this though:
"One, the CTO couldn't be a first rate hacker, because to become an eminent NT developer he would have had to use NT voluntarily, multiple times, and I couldn't imagine a great hacker doing that; and two, even if he was good, he'd have a hard time hiring anyone good to work for him if the project had to be built on NT. "
I don't agree fully with this (I will explain):
"Really there should be two articles: one about what to do if you are yourself a programmer, and one about what to do if you're not. And the second could probably be condensed into two words: give up."
And this is part of my explaination:
"I call it the design paradox. You might think that you could make your products beautiful just by hiring a great designer to design them. But if you yourself don't have good taste, how are you going to recognize a good designer? By definition you can't tell from his portfolio. And you can't go by the awards he's won or the jobs he's had, because in design, as in most fields, those tend to be driven by fashion and schmoozing, with actual ability a distant third. There's no way around it: you can't manage a process intended to produce beautiful things without knowing what beautiful is."
The problem is that a great hacker my have no clue about front end design. Recently I programmed a water sample evaluation program that had been done twice before. The first program was out of data and never really made it past beta. The second used a slick gui interface and was upto date. And yet, I was told mine was better. The reason is not that I am a great hacker (although I did program it in python
), the reason was that I actually know what people who use the type of program want. The complaints are not against the gui - but how it operates. If the PM had spent an hour with an end user and really paid attension I never would have stood a chance of making anything but a bad knock off.
I liked the article, but its a bit to much of a pep rally for programmers. There is some good material - but it gets offset by farsweeping and unfounded generalizations.