|
|
|
|
|
by gary4gar
5471 days ago
|
|
Just 3 things: 1) Things get broken all the time:
so instead of playing the blame game & doing name calling.Expect that things will break & assume there will be bugs. Focus should be fixing the problem ASAP & _then_ doing an analysis on what went wrong. so corrective measures can be taken so the same problem does not reoccur again. 2) 9 Women Can’t Make a Baby in a Month:
If you had more capital, could you finish things faster? NO, look what happened to Color(about 200employees, IIRC) & compare that to instagram(10-12 people) . In software eng, More resource does not necessarily mean better product. 3) Don't bother about coding, but test the shit of product to provide honest constructive feedback. Plus, be the public face of the company. technical people prefer doing programming rather interacting with random bunch of strangers. These are the main three ones, I could think of top of my head. Hope it helps :) |
|
I'm sure that most of technical co-founders LOVE to tell about what they are building, just... leave most of business crap out of the way and it's perfect!
Non-technical? Be supportive, that's your role.