Hacker News Reader

Comment by marktangotango | Hacker News Reader

This x1000. The last thing you should do is withdraw, and leave everyone high and dry. I've seen this situation, where the 3 remaining of the original cohort, for some reason, resented the new CTO, and basically abandoned the company. Only reason they're still here is they have an ownsership stake and are friends with CEO. They could've been hugely impactful to the success of the company, but instead, they're sitting back to watch the everyone else fail.

Also, with this crew in particular, they really weren't that good. They begat a lava layered monstrosity that doesn't scale and isn't maintainable. Make sure that's not you.

View on HN

What is wrong with leaving everyone high and dry? The CEO has no qualms about doing that to devs.

If an engineer leaving puts the company in a bad spot, then they are understaffed and need better management that can foresee and handle those transitions before they happen.

It's all part of proper engineering culture.

This is what happens when one person stops communicating to another due to lack of awareness; the other assumes the worst, and stops reciprocating. They are the only one who knows what's going on, yet it almost always comes down to them saying "Why should I be the first to re-establish communication?". You should do it because you're an adult, and the other person isn't a mind-reader; if you don't, you don't deserve any sympathy when the shit hits the fan.

I think even before you bring responsibility into the picture, there's a lot for each actor in this situation to gain from reestablishing communications(I certainly can't see what they would lose, except for face). This is assuming the other party is mature and rational though.

You're suggesting he owes them something, and it really sounds like he doesn't - they've passed him over for career advancement, so he needs to find somewhere he'll be appreciated

I don't understand why this attitude is a problem in this context.

It's their last and only pressure point in the political game that happens in the company.

If you don't feel that your skills are fairly compensated and you can't leave (due to contracting or vesting time) you don't have any other options.

Being a dick is not an option or a negotiation tactic, it is just that being a dick. Note I'm speaking to my experience, where tbe people in question do everything but actively sabotage the CTO in question.

"Being a dick is not an option or a negotiation tactic"

I disagree. Leaving is not "being a dick", it's looking out for yourself. If you don't, nobody else will. It's apparent this is the case with the OP: He was pretty much built the entire company up and was there for the company when they needed him (I would imagine late hours, weekends, etc).

Now that they don't need him anymore, they pushed him off to the side. I've heard this story 1000 times and experienced it first-hand.

I don't work for startups for exactly this reason. If I'm spending my life building your company, I better be getting 50% in equity. It's really not worth the fooseball table in the lunch room and the Red Bull in the fridge. This is why you need to get the young and naive to fill these roles.

I agree, leaving is not being a dick. Staying and not helping, or actively hindering new staff through lies and misdirection about implementation details of a complex application in a complicated domain is.

Reply on news.ycombinator.com