After landing a lucrative job at a tech startup, I had made a terrible mistake

Post by mcguire » Tue, Dec 11, 2018, 3:53 PM UTC

com2kid wrote: post #3

I am incredibly sick and tired of this stereotype: > The most common is the engineer who, slaving for hours in the proverbial garage, programs his (or, infrequently, her) way to glory and gets showered with millions by venture capitalists. He is the tech cliché—nerdy and socially awkward. At least 90% of the technical co-founders I know are well spoken, well dressed, and perfectly capable of attending social events.…

Post by SpicyLemonZest » Tue, Dec 11, 2018, 3:59 PM UTC

wpietri wrote: post #113

dmix wrote: post #35

Earlier quoted context omitted.

Working for a big company/megacorp without valuable good stock options/bonuses on weekends and off-hours is dumb and abusive. On the other hand these startups are voluntary organizations. You choose to work there or not. I don't see anything wrong with a company deciding on a culture/work enviornment which attracts people who are very dedicated to the company (and hope to be rewarded in the long term as such) and are…

> On the other hand these startups are voluntary organizations. You choose to work there or not. I think this sounds good in theory and is very shaky in practice. For example, look at indentured servitude [1], where people can sell themselves into time-limited slavery. Once common, it has been banned. You will find people suggesting we bring it back while waving the banner of "freedom". It's especially erroneous here…

Post by diminoten » Tue, Dec 11, 2018, 4:05 PM UTC

Delmania wrote: post #81

Whenever I find myself falling for this, I keenly remember the advice given to me from Your Money or Your Life, which is that you are at work for 1 reason and 1 reason only: money. Many people say they work for other reasons, like socialization, meaning, etc. Robinson (the author) makes a point that you can find these things in volunteer activities, and that your loyalty ends at the paycheck. Your company will not he…

Post by mdpopescu » Tue, Dec 11, 2018, 4:06 PM UTC

raducu wrote: post #93

titzer wrote: post #80

Earlier quoted context omitted.

I will think of this every time I see a getter/setter pair on a class. The illusion of modularity and encapsulation with net negative in code quality.

Let's not forget about one Interface for one Class, because that adds flexibility in the future :)

Post by forkerenok » Tue, Dec 11, 2018, 4:13 PM UTC

scarejunba wrote: post #73

pcunite wrote: post #6

Culture is an obsession at start-ups. They talk about it nearly as much as they talk about sales targets. Its a signal for: don't apply here if you're over 40.

Believe whatever you want. But I'm never hiring a guy whose belief is that as a developer his job is only building whatever some person thinking about the product wants. I want to work with engineers who want influence over the product. That's a culture difference. I'm never hiring a guy who thinks it's his job to only write code in the stack I tell him to under the rules I place him under. I want to work with people…