News for hackers. Stuff that matters.
Re:Ask HN: Senior Devs, what career have you moved on to avo... by giantg2 on Monday October 25, 2021 @12:10PM (#28989475)
I think you're taking my comments out of context and changing the subject.

First, you seem to have dropped the percentage topic, which you had initially talked to. It seems like you're just changing the topic for the sake of arguing something on a tangent (isn't that against the rules here).

Now you seem to be talking about people who are too good to do things. Which is entirely different than what I'm talking about - appropriately staffing a team based on expected tasks and minimizing budget.

Re:Ask HN: Senior Devs, what career have you moved on to avo... by PaulHoule on Monday October 25, 2021 @01:11PM (#28990360)
No, I'm rejecting your construction of "junior" and "senior".

Tasks are not really "junior" or "senior" tasks but really tasks that juniors or seniors could do with different results in terms of time, cost, quality, etc.

Sometimes a "junior" is more experienced at the latest methods. This is one thing you see with medical doctors or electrical engineers, that many people go through their careers and keep using the same methods they used at the beginning. (Think of the old saying that "Science advances one funeral at a time")

For instance 20 years I go didn't expect an undergraduate student to have any idea what version control is, today I expect them to have a Github account.

Re:Ask HN: Senior Devs, what career have you moved on to avo... by giantg2 on Monday October 25, 2021 @01:44PM (#28990821)
"Tasks are not really "junior" or "senior" tasks but really tasks that juniors or seniors could do with different results in terms of time, cost, quality, etc."

You are putting words in my mouth. I never called the tasks "junior" or "senior". Looks like you agree with me, but felt the need to argue anyways.