3 ms·

To the author; If you're having trouble finding specifically "bi-directional video" guys you may want to expand your search to VoIP devs. Many of the challenge

To the author; If you're having trouble finding specifically "bi-directional video" guys you may want to expand your search to VoIP devs. Many of the challenges are the same, and the protocols. It is also likely that they will have more experience. A lot of large telcos have dropped big money on VoIP over the last decade. So there's a larger pool of talent available to draw from. Also, consider the tone of your post, and your attitude in general. Devs have "Red Flags" we look for as well. You give off several. Consider that many people on this board have the skills your looking for, and/or know someone who does. Pay attention to what you are telling us.

nickfromseattle 15y ago
What are the author's red flags?
- johngalt 15y ago
  "don’t let go of key team members for replacements until the replacement starts" Not an inspiring message to future key team members. "We begun parting ways with our developers, started to wind down most of our NYC operations" So the next smart dev is in Bangalore, guess that means he'll shut it all down again right? "The highs and lows continued. I realized we shouldn’t support a full production operation until our product was completely done, tested, etc." Better to think about what you absolutely require compared to the resources you have to 'fully complete' them. "That Friday, I let Ted know that we need to trim down the team further..." Then Ted quit the following day with a nice email detailing how things had changed in the last 36 hours and the ways he'd like to help him recruit a few engineers read between the lines. "the single most unprofessional thing I have ever heard of" Sending a nice resignation letter is the worst they have ever heard of? Frankly 90% of this post is detailing poor business and hiring decisions. Then blaming Ted for poor behavior rather than accept responsibility. The author likes to bite off hard technical challenges then complain he can't find someone talented enough to chew it. How is it that he even knows what he can accomplish before he's found his co-founder?

nickfromseattle 15y ago

What are the author's red flags?

johngalt 15y ago
"don’t let go of key team members for replacements until the replacement starts" Not an inspiring message to future key team members. "We begun parting ways with our developers, started to wind down most of our NYC operations" So the next smart dev is in Bangalore, guess that means he'll shut it all down again right? "The highs and lows continued. I realized we shouldn’t support a full production operation until our product was completely done, tested, etc." Better to think about what you absolutely require compared to the resources you have to 'fully complete' them. "That Friday, I let Ted know that we need to trim down the team further..." Then Ted quit the following day with a nice email detailing how things had changed in the last 36 hours and the ways he'd like to help him recruit a few engineers read between the lines. "the single most unprofessional thing I have ever heard of" Sending a nice resignation letter is the worst they have ever heard of? Frankly 90% of this post is detailing poor business and hiring decisions. Then blaming Ted for poor behavior rather than accept responsibility. The author likes to bite off hard technical challenges then complain he can't find someone talented enough to chew it. How is it that he even knows what he can accomplish before he's found his co-founder?