3 ms·
FWIW, I never claimed to build everything myself… and we (my husband & I) made extensive use of freelance developers, support people, etc. Where do you think th
by ahoyhere 14y ago
FWIW, I never claimed to build everything myself… and we (my husband & I) made extensive use of freelance developers, support people, etc. Where do you think the $200k on Charm went? Not to my salary :)
Charm would have been an enormous commercial success based on all the indicators, but we belatedly realized that running it would entail a stressful type of business we didn't want. Big fat "Duh" there. I stake full claim of my mistakes and warn others about it.
This may sound like me twisting definitions but I don't think buying-an-existing-product is the same as outsourcing development, even if it is your only product. In the former, you've got something that already exists, that you can look at and try and poke around in; in the latter, you've got some rough designs and the hope that you picked the right freelancer.
I've seen so many people take the latter course - true outsourcing - and flop around til their money was all gone. Despite trying very hard not to be a party to it, so many of my clients were like that. I eventually had to come to the conclusion that I could push them to cut back features and launch, but it wasn't my job to refuse to do what they asked just because it was dumb.
On the other side, if you fully outsource your product, from scratch, what do you do if (as I mention in the transcript) you have a falling out and suddenly there's a major bug? You not only can't fix it yourself, you aren't sure if you know what it is, how to know if the person you hire can fix it, how to know if they've done a good job or not… plus your track record for hiring is already bad. It's a kind of helpless death spiral — tiny cuts leading to arterial spray.
Sidebar: This has made me realize just how little I know about Rob's origin story, so I'm going to have to fix that :) And by "this" I mean "this discussion" and not "arterial spray," ha!
- charlieirish 14y agoSo, are you saying always keep the core development/design internal? Regarding Charm, it wasn't always clear to me why you shut it down. You mentioned it here: http://news.ycombinator.com/item?id=4814598 http://news.ycombinator.com/item?id=4814598 which received some positive and negative comments. I'd rather not start that debate again but it would be interesting to hear your thoughts on whether the development of Charm was the issue i.e. internal vs. outsourced. Rob has recently detailed his story on the excellent (and fairly new) Product People Podcast (from mijustin): http://productpeople.tv/2013/01/16/ep09-rob-walling-part1/ http://productpeople.tv/2013/01/16/ep09-rob-walling-part1/
- ahoyhere 14y agoThe issues with Charm have absolutely nothing to do with my position on outsourcing. They're two unrelated points that occurred in the same conversation :) It wasn't the development that was the issue. It was the preview of things to come, running an infrastructure product, and the general inability to hire somebody to just take that over for us entirely. Do not want. As for "core"… what does "core" mean? If you are helpless to fix things in your product, even on a stopgap emergency basis, you are going to be in for some miserable times. Unlike writing or design, code is completely impenetrable if you don't know a lot already.