Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> You know, your typical “software engineering” work.

“Typical” work, done well and on time with good production reliability, is often hard to get.

Perhaps it’s a sign of your seniority that you think that’s all typical. I’ve seen people release buggy code with no tests, metrics, or monitoring and think they were finished with it. That gets fixed when the more senior engineers step in and demand higher standards.

It’s sad that the baseline for quality in the software industry is so low, but that’s how it is.



The thing is that:

Junior -> needs monitoring ~weekly

Senior -> does eng work reliably and on time, can lead a junior or maybe a few but doesn't have to

Staff -> leads Seniors (plus maybe some juniors directly)

Grandparent is mentioning that in their org there are plenty Staffs that do not lead anyone.


Yeah. As I said the rubric makes it look like every staff engineer must make Kubernetes run in a WebWorker or invent git in each quarter.

They are written to make a case for not prompting people. They are not guideline


> ...the rubric makes it look like every staff engineer must make Kubernetes run in a WebWorker

No words for an insight as incisive as this.


>>> They are written to make a case for not prompting people. They are not guideline

Insightful - thank you




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: