I started to read the article and it sounded like a very short version of the book. I read the book (on a recommendation from HN) and took a lot from it. In p

I started to read the article and it sounded like a very short version of the book. I read the book (on a recommendation from HN) and took a lot from it. In particular I found the dynamic between the programmer who made the technology and himself (who did the business development) interesting. He made the programmer what I thought was a fair deal, worked his ass off selling, and things grew fast. The programmer got really pissed and created all kinds of headaches. Reading this gave me a chance to evaluate any future business relationships I might have as a programmer. Overall the book isn't on my must read list but I still thought it was pretty good. I