Great Hacker != Great Hire
Eric Sink discusses Paul Grahams Great Hackers essay in some detail. He argues that Great Hacker is not nesseserily great hire. His viewpoint comes from small but successfull ISV.
I must say I agree both with Eric Sink and Paul Graham. They are both right. Eric's idea of ISV is company that serves customers need in short term (basically makes features buy request). PG's idea is ISV that corrects customers behavior. Marketing term to latter is strategic IT consulting. If you see your firm as ISV you are paid buy lines of code and features you provide. If you are solution provider and consultant, you go into your customers prosesses and set them right.
Btw. Great Hackers can understand issues of customer satisfaction etc. They can build wery clean interfaces aroud all this ugly stuff. You can buy all this code slave stuff from others (small software firms aroud you).
One issue with software engineering is that if your fundamental design is flawed but your software deliveres first 1-10 years easily and it continues to grow organically with small increments buy not so great hackers, what you have is money machine. You can milk your customers decades and they have no other option than pay.
The moral of above chapter is this. Great software and great business don't nesseserily go well together. There is only so and so many Great Hackers, great software. If your businessplan depends on great desingn you are more likely to fail than if it's placed around ever changing "business standards" and temporary customer needs. Great graftmanship may see this as immoral thing and refuse to work.
I am myself sometimes a customer for Great Hackers Co. and this gives me secure feeling. My contractor in Creat Hacker company has helped me to make sound long term business descision. Great ISV:s are not only software jocks, they also contribute to strategic desicions. That can be called consulting.
I must say I agree both with Eric Sink and Paul Graham. They are both right. Eric's idea of ISV is company that serves customers need in short term (basically makes features buy request). PG's idea is ISV that corrects customers behavior. Marketing term to latter is strategic IT consulting. If you see your firm as ISV you are paid buy lines of code and features you provide. If you are solution provider and consultant, you go into your customers prosesses and set them right.
Btw. Great Hackers can understand issues of customer satisfaction etc. They can build wery clean interfaces aroud all this ugly stuff. You can buy all this code slave stuff from others (small software firms aroud you).
One issue with software engineering is that if your fundamental design is flawed but your software deliveres first 1-10 years easily and it continues to grow organically with small increments buy not so great hackers, what you have is money machine. You can milk your customers decades and they have no other option than pay.
The moral of above chapter is this. Great software and great business don't nesseserily go well together. There is only so and so many Great Hackers, great software. If your businessplan depends on great desingn you are more likely to fail than if it's placed around ever changing "business standards" and temporary customer needs. Great graftmanship may see this as immoral thing and refuse to work.
I am myself sometimes a customer for Great Hackers Co. and this gives me secure feeling. My contractor in Creat Hacker company has helped me to make sound long term business descision. Great ISV:s are not only software jocks, they also contribute to strategic desicions. That can be called consulting.

