The point went over your head, in any failed dynamic there are always mistakes made on both sides. I'm trying to encourage her to think deeper (not write) about it beyond not catching the "warning signs" which places her in a victim position. Whether she was or not, victim cycles create repeat patterns until the person sees their own role in it.
I'm encouraging psychological healing. I've very much been through a very similar experience.
[EDIT]
It actually sounds like it turned out well since she did end up with a solid co-founder relationship anyway. I'm leaving this up for posterity but now think my thoughts on this are unwarranted.
I've been using this to test the usability of our internal management with the team and figure out bugs. It's fun to send recorded snippets of future functionality too. Love it!
Interesting aspect i'd never thought of. When you haven't working in (or with) HR before I guess you might not think of things like recovering alcoholics - or even company liability.
It seems a lot of startups ignore these issues for a hope of garnering another scoop from the talent pool.
Had to jump in here. Just because you have a person preference of complete sobriety whilst working shouldn't mean it's a policy for everyone.
For example:
• I work best in the early mornings - does this mean everyone should come in from 5am?
• I find it hard to work at a stand-up desk - nobody can use stand up desks anymore, sorry.
• I feel drained after going to the gym before work - nobody can go to the gym before work, it will stifle your creative thinking.
• Wearing long pants (versus shorts) makes me uncomfortable (i.e. unproductive) - no more long pants in the office.
If they make me unproductive - fine. That's me. As for making it a company issue - tell me which of the above options go beyond personal preference.
I have the same concerns (although I already have apps using Parse in the wild!):
• Will FB kill off Parse? Seems quite unlikely in the short term, but in the long term?
• Are they going to try and force any integrations with FB?
• Will Parse continue to improve (they've done a lot of this recently!) or will it dwindle as others move faster?
• Data / Privacy - what's going to happen with those going forward? These always are a concern in people's minds when FB comes up.
• Facebook's APIs / Developer Support is SHIT... will this happen to Parse too?
Totally agreed that Parse kicks ass, which is why we bought them; we're looking forward to working with the team to continue to improve it!
As a brand new member of the team, I'm really keen to hear more about how we've failed at our APIs and developer support and what we could do to be way better.
Late last year, I've tried to integrate Facebook into two tiny iOS apps. It sucked, and I'm not going to touch Parse in the future.
One of the few things I needed was an app request dialog. It didn't seem possible from the SDK docs (at least not clearly so), the only way was to use the deprecated global Facebook object:
There was no definitive list of possible values for the dialog name or parameters either. Apparently "message" was being ignored, but only for "feed" dialogs...? Apparently there is a replacement now, but it's still in beta. How am I supposed to tell my clients what is possible (and sustainable) and what isn't?
It's a matter of what it's worth to you. What risks are you willing to take?
There are developers who may charge $700/hr, but you've chosen to go with a developer who charges $100/hr because that's what you need at this stage. If he made a mistake, it's not likely to cost you EVERYTHING to fix up. Somebody points out the bug / issue and you can hire him to sort it out and push out an update. Speak to a developer who works at a law firm ;)
Conversely, people device to go with a $700/hr lawyer because of their experience and reputation. You're paying for them to not make a mistake because it may just cost you EVERYTHING. It's not a mistake you can fix after it's found. Something wrong with your patent? Contract? Not something you can say 'oops, it's fixed now' to.
