Hacker News new | ask | show | jobs
by brailsafe 1466 days ago
Employees should never feel like the company is theirs. Unless you have a real seat at the table, you should assume you have no influence over the business. That's what being an employee is (with no actual shares). You give up the risk by being an employee, and your only negotiating power is leaving.
4 comments

"give up the risk by being an employee"

I have observed many folks join startups as employees, take on risk without understanding it and without a clear benefit.

> Employees should never feel like the company is theirs.

Imagine you've put your soul into it, and some years later they tell you that you can no longer pursue your vision and respect your users, and you're now a mere executor. Your opinion no longer matters, and the fact that you have one at all is a nuisance for the new management.

I personally don't work for the money, for me the money is very much a side effect of making the world a better place.

> Imagine you've put your soul into it, and some years later they tell you that you can no longer pursue your vision and respect your users, and you're now a mere executor. Your opinion no longer matters, and the fact that you have one at all is a nuisance for the new management.

Ya, my argument is that people are absolutely naive to do this, for the reasons I mentioned.

> For me the money is very much a side effect of making the world a better place.

That's what they want you to believe. People sure as hell weren't clanging pots and pans for the software developers who instead of writing code all day in their ivory tower in downtown SF, only to leave and walk past human feces, needles, and suffering, instead got to go home and write that code from their $5k 1bdr apartment. If you can try to choose your industry more carefully, that's great, but don't lie and tell me you're paid so well because of your noble contribution to the human race.

People should try and be good to others, and if they can afford it, work for companies on products that don't actively harm people, but when they can't pay you or their stakeholders decide that's irrelevant, you can leave.

I'm non-US, and English isn't my native language either. But I have been to SF and have walked around the downtown. That stark contrast of there being so many homeless people just across the street from the building where Google I/O was held, where some of the best IT workers from all around the world gathered, that was something very unusual to me. Something of a culture shock. It's definitely not the norm where I'm from for people to not be able to afford a place to live.
> You give up the risk by being an employee

This is not true. Employees carry salary risk. For most people, unplanned loss of salary is catastrophic in the short-term.

In the U.S and maybe Canada, that's true, so you have to be cautious about which company you join. I'm actually facing this right now, but I'm a contractor, and by accepting that the risk of technically running my own business, I can also just stop providing my services if they won't be paid for. Employees can also do this though.
That sounds like you feel pretty helpless. Personally, I find that I have numerous avenues of negotiating power, even without unionization:

1. Do I recommend the company to my network? I can make it a lot cheaper or more expensive to hire.

2. How do I spend my time? All my technical choices will make certain changes easier down the line, and others harder. I work hard to understand the business context & help those choices serve our shared goals, but the emphasis there can be on "shared".

3. How much do I streamline my own work? I can work efficiently, or I can wait for that build to finish and that PR to be approved and merged before I move on to the next thing. This can be a particularly effective way to incentive investment in a platform team & build tools, if I'm not allowed to just fix them myself.

4. What do I collaborate on with my coworkers? We can pick priorities we care about, and negotiate together for specific improvements. I've gotten more vacation time, better computers, bigger screens, paid on-calls and time to fix bugs all just by talking with people about what's hard about our work.

5. Insisting on pushing improvements to open source software upstream if we are going to use the libraries at all. The company could decide it wants to write everything entirely in house, but as long as we are using open source software I personally only make changes to it that we are going to push back to the community.

And I am sure there are more: those are just the ones I've used recently.

Yhose are all nice when negotiating working from home or something similarly minor - but when it comes to foundamental business model, these things are unlikely to move the needle.
That's pretty much what I was thinking while reading it. The difference between doing your work, and doing your work better than you're expected, is often unrewarded with any measurable security, probably because they're non-functional requirements and it's hard for some manager to sell their boss on the RoI. It's similarly hard to measure, if they'd even let you in on that data, how much of a minor influence you had on the business financially. Sales people meanwhile can just say "I sold this company on a $2m contract for services over the next 2 years"