If you get to senior level then most of your job probably is not writing code, but planning things out. The code is largely an implementation detail.

At least that's how it was for me, maybe other peoples' careers are different.

▲

lelanthran 3 hours ago | parent | next [-]

> If you get to senior level then most of your job probably is not writing code, but planning things out.

If they're so good at banging out code now, they're coming for that too, you know.

▲

tombert 3 hours ago | parent [-]

I don't necessarily disagree, but there's gotta be a name for some kind of "infinite extrapolation" fallacy, where you assume that the current rate of progress will continue indefinitely.

That might happen, but I don't think it's implied, at least given literally every other bit of technology that has ever happened in history ever.

	▲	lelanthran 3 hours ago \| parent [-]
		> I don't necessarily disagree, but there's gotta be a name for some kind of "infinite extrapolation" fallacy, where you assume that the current rate of progress will continue indefinitely. I am not assuming they'll continue indefinitely, but it's a small step from writing code to planning out the code to write, and another small step from planning a coding project to planning a software project, etc. These are all small steps, and because the act of specification + planning paid less than specification + planning + programming, what reason do you have for thinking that specification + planning is valuable enough to keep the salaries the same as specification + planning + programming?

▲

bluefirebrand 4 hours ago | parent | prev [-]

Yes, my career has been different. At my workplaces seniors still have to code because they dont want to hire juniors

The "planning things out" has moved to another layer, called "architects"