Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

My salary as a full-stack developer

remotehunt.com

Post reply on HN
Print view View original

121–126 of 126 posts

Re: My salary as a full-stack developer

#121

Post by decafninja »

Philip-J-Fry wrote: post #82
the_only_law wrote: post #26

FWIW I make similar, less pre-tax but more post-tax, though with maybe a third of the experience. I’ve seen the comments about “just go to FAANG” and it’s one of those odd dualities I see on HN. On some threads, I see comments full of how their interviews are IQ proxies and how FAANG only hires the best or top X% so it’s not viable for most devs. On the other hand there are plenty of comments that just suggest casual…

I wanna know how many people working at a FAANG are actually employing the hardcore development skills we're led to believe we need to work there. Like, surely most people are just working on pretty generic software components that the average developer could.

From what I hear from my friends that got into FAANG, at least none of them seem to do.

My best friend's FAANG job sounds incredible mundane to be honest. An entire team seems to be dedicated towards working on the backend piece of what seems like a very small feature, plus another entire sister team is working on the frontend piece of same feature. Granted there is probably a level of scale involved that adds complexity, but just hearing him talk about what he and his team does makes my unsexy non-tech company work more interesting.

Re: My salary as a full-stack developer

#122

Post by SAI_Peregrinus »

Jenk wrote: post #99
SAI_Peregrinus wrote: post #94

Earlier quoted context omitted.

I agree, but I'd say story points are themselves a mistake. In the end, what matters is time. Story points don't matter if the schedule slips. So you either get story points and no way to keep a schedule, or story points + time estimates (with useless story points), or just go with time estimates. The schedule may still slip, since estimating time is very difficult, but at least some of the time it will be correct (o…

The entire purpose of introducing story points is to move away from time estimating. Time estimating is broken and inaccurate. Complexity estimating is marginally more accurate but still with a wide range of inaccuracy. Instead teams should focus on delivering value incrementally, then using metrics over those increments as a measure for future increments.

And yet there's still a product, still a date that product will ship to customers, and therefore time estimation is at some level necessary. Often there's a factory building something, physical shipping, late fees, etc. If you're solely responsible for setting all your own deadlines, then there's no need to estimate time. That's very rare.

Time estimating is broken and inaccurate. But that doesn't mean it's unnecessary, or that one can just give up on it. Teams should focus on delivering value incrementally, then using time taken as a metric (among others) over those increments as a measure for future increments.

Re: My salary as a full-stack developer

#123

Post by p1esk »

misterremote wrote: post #105
terminalserver wrote: post #63

This feels like a somewhat disingenuous promotion for the remote hunt website. Is it real or not?

Sorry if that looked like this for you. It's 100% real. And today I had a call with startup. I had some numbers to back me up now with HN comments. But they basically said that they don't have any more money to pay me, so we just need to get by with what we have as a team. I was like, what should my motivation be in this? It's not my startup...

what should my motivation be

Equity

Re: My salary as a full-stack developer

#124

Post by p1esk »

misterremote wrote: post #106
nerbert wrote: post #54

It does not answer the question he asks but if he’s as good as he says, he can just refuse to log his hours.

But I can't. I mean... okay I can. I can just say: "no, I don't track my time for you. this is who I am and I just don't track time." And then they ask: "why?". What should I say then? :| Well, there are a few real reasons why I don't want to track my time: 1. I just don't like to track time. I know that I'm good at what I do and can finish tasks very quickly. I guess it's a bit like my ego thing I admit. I somehow h…

There are plenty of better startups in US who would want to hire you.

Re: My salary as a full-stack developer

#125

Post by Jenk »

SAI_Peregrinus wrote: post #122
Jenk wrote: post #99

Earlier quoted context omitted.

The entire purpose of introducing story points is to move away from time estimating. Time estimating is broken and inaccurate. Complexity estimating is marginally more accurate but still with a wide range of inaccuracy. Instead teams should focus on delivering value incrementally, then using metrics over those increments as a measure for future increments.

And yet there's still a product, still a date that product will ship to customers, and therefore time estimation is at some level necessary. Often there's a factory building something, physical shipping, late fees, etc. If you're solely responsible for setting all your own deadlines, then there's no need to estimate time. That's very rare. Time estimating is broken and inaccurate. But that doesn't mean it's unnecessa…

Hence my point about using measurements from historic actuals to give a forecast instead of asking for explicit estimates. Sitting some devs down and asking them for gut feels is far less accurate than comparing to previous increments.

Re: My salary as a full-stack developer

#126

Post by SAI_Peregrinus »

Jenk wrote: post #125
SAI_Peregrinus wrote: post #122

Earlier quoted context omitted.

And yet there's still a product, still a date that product will ship to customers, and therefore time estimation is at some level necessary. Often there's a factory building something, physical shipping, late fees, etc. If you're solely responsible for setting all your own deadlines, then there's no need to estimate time. That's very rare. Time estimating is broken and inaccurate. But that doesn't mean it's unnecessa…

Hence my point about using measurements from historic actuals to give a forecast instead of asking for explicit estimates. Sitting some devs down and asking them for gut feels is far less accurate than comparing to previous increments.

Certainly! "Gut feel" is a shit way to do time estimates. It's a programmer way, not an engineering way. Of course it's harder to get historical data for software than for other engineering fields, because software is so new. But it's not impossible, and if companies don't even collect the data (due to using story points) they'll never manage to get forecasts when they need them.
Post reply on HN