2,030 karma · joined August 1, 2008
[1] at least to me
[2] http://kylewritescode.com/
[3] that's not to say I don't care about it generally speaking; I do strive to be thoughtful, helpful, and someone that people respect.
Our app isn't huge, but still pretty complex and comes with a bit of a learning curve. The dev I hired I'd originally met on Forrst, and that provided a nice opportunity to get to know him and his process for a bit before we started discussing working together. It's worked out beautifully so far.
I hear you on managing others -- it's been a learning experience for me, and I know I'm not great yet, but getting better all the time. From my perspective, I've tried to approach this from the standpoint of "would I enjoy working for me". Also, I think it's important to keep things in perspective -- two devs is still really small, and should (to me at least) feel more like a partnership than a more formal manager/employee relationship.
That being said, I'm curious if you've been able to gather any data on why they're not sticking around. Even an informal exit interview over coffee or something. Seems like that could be useful in determining what to do next.
I'm still in awe at how well this turned out. Huge kudos to you both. And, made me realize: Clearly we need to do a better job keeping tabs on awesome collabs like this. I'm certain there must be more.
I'm still trying to figure out the best way to angle this, but my ideal customer is an "idea guy" who does have the means to pay, an interesting idea, and "gets it" with regard to what it actually takes to build a product.
I do like the idea about involving some kind of idea sanity check, though I'm kind of doing that as folks contact me — I'd rather tell them that it's not really a viable idea as is, and spend a little time working through that, vs. take their money for the 2 hours or MVP product just because I can.
That being said: PHP, Ruby, some Python; Mysql, Postgres, Mongo.
Also, that JSM post never gets old.