[richardjortega]

Why assume my time estimate is wrong? I asked him for the estimate of hours. He doesn't include "research" time, I told him I'd pay for that time - he doesn't think it should be counted. In previous projects we've worked on, he has always underbilled we wanted to make sure that didn't happen this time.

I managed our frontend dev team and I personally estimated their hours (since I've managed software teams before) and got only 10-20 hours over.

I disrespect him because he started disrespecting me. Why assume the non-tech founder is always the bad guy?

One email for instance - "We have our life savings in this. This one feature update has taken over three weeks, please give us an ETA. Can another developer assist?" Answer: "Guilt doesn't work... I won't be able to see this until Friday. Sure another dev can take a whack at it, I'll add him to repo" (Email sent last Tuesday).

[coffee]

"I disrespect him because he started disrespecting me."

That is very immature.

"Why assume the non-tech founder is always the bad guy?"

Because in most cases this is true. And when you write a post titled "My programmer is a dick..." what do you think people are going to assume?

You demonstrate a lack of maturity and understanding of how to successfully engage with others. You came here asking for advice, don't be so defensive.

[richardjortega]

I debated responding to you. But I will, because I'm trying to truly resolve this situation with my dev.

I don't know the first thing about you and I won't assume. I'm asking for comments on what to do next. Sorry if I called a "person" a dick, and sorry if that person happened to be a fellow "programmer".

Would you have replied to this post had I posted "I'm having difficulty with my programmer meeting deadlines"

[PonyGumbo]

>"We have our life savings in this."

Look, I get the stress of the situation, but using emotional guilt is a terrible way to try to manage people. If he's not doing the work, let him go, and make sure you set clearer expectations for your next hire. His response doesn't strike me as any more inappropriate than you dropping the life savings bombshell on him.

[richardjortega]

I wasn't trying to manage him, just that specific example was for a client who waited for three weeks for logins. All I need was an update (requested politely 4-6 times prior) and received no responses.

Those emails aren't the only ones, usually he is couple words per email. But you are right, dropping a "life savings bombshell" on him wasn't right either.

I think we didn't set expectations clearly with him because he was a friend and we worked together on various client work I didn't think anything of it.