2 ms·

It's a gamble, but one that makes a lot of sense, in a very selfish way: Building a career in one place without trying to take shots upwards is not good: Progra

by hibikir 11y ago

It's a gamble, but one that makes a lot of sense, in a very selfish way: Building a career in one place without trying to take shots upwards is not good: Programmers get more pay by changing jobs, not by being very patient and hoping they'll get noticed eventually. So once you are in a place that isn't a tiny startup (which is in itself a risk), you should take risks for big internal payoffs. If those risks pay out, great. If they don't, then just go somewhere else and try again. Few things are sadder to me than seeing to talent that is mildly disgruntled, being a key part of their organization, underpaid, not taking risks, just hoping that someone would notice them and pay them appropriately: Providing value without immediate recognition is just asking people to find ways to make you provide more value without reward, as you've already proven that you are too afraid to demand fair pay. I've worked with people that had spent 10 years at a company, working on my team, as pillars of the company, getting paid 60k/yr, sitting next to a contractor billing 125/hr

toomuchtodo 11y ago
> Building a career in one place without trying to take shots upwards is not good: Programmers get more pay by changing jobs, not by being very patient and hoping they'll get noticed eventually. So once you are in a place that isn't a tiny startup (which is in itself a risk), you should take risks for big internal payoffs. If those risks pay out, great. If they don't, then just go somewhere else and try again. > I've worked with people that had spent 10 years at a company, working on my team, as pillars of the company, getting paid 60k/yr, sitting next to a contractor billing 125/hr The lesson isn't to take big internal risks. The lesson is to engineer your finances to allow you to weather the volatility of being a contractor, and then be the contractor. Everyone shits on the idea of the contractor, when they're doing exactly what they're incentivized to do: maximize the value they extract in the shortest period of time possible, while providing value to the organization they're working for. Screw your equity, your business culture/hierarchy, and paying your dues (colloquially known as "F*ck you, pay me").

by hibikir 11y ago

toomuchtodo 11y ago

> Building a career in one place without trying to take shots upwards is not good: Programmers get more pay by changing jobs, not by being very patient and hoping they'll get noticed eventually. So once you are in a place that isn't a tiny startup (which is in itself a risk), you should take risks for big internal payoffs. If those risks pay out, great. If they don't, then just go somewhere else and try again. > I've worked with people that had spent 10 years at a company, working on my team, as pillars of the company, getting paid 60k/yr, sitting next to a contractor billing 125/hr The lesson isn't to take big internal risks. The lesson is to engineer your finances to allow you to weather the volatility of being a contractor, and then be the contractor. Everyone shits on the idea of the contractor, when they're doing exactly what they're incentivized to do: maximize the value they extract in the shortest period of time possible, while providing value to the organization they're working for. Screw your equity, your business culture/hierarchy, and paying your dues (colloquially known as "F*ck you, pay me").