2 ms·

So, 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:

So, 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 ago
The 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.