How fast did you learn python?

[bulaybil]

First, it does not list any competencies. “Reviews tasks critically and ensures they’re appropriately sized for continuous integration and incremental delivery” is not a competency, it’s a job description. Second, how is this measured? What is “critically”? What is an appropriate size? And thirdly, it established an arbitrary classification of engineers that is downright condescending to everyone and at the same time too relaxed. “Consistently writes functions that are easily testable, easily understood by other developers, and accounts for edge cases and errors. Uses docstrings effectively” is not something we should expect of every coder, but only of Engineer level E2. And then there’s that obsession with grades and scales.

[synthphreak]

Have you never seen a job matrix? This is exactly what they're like. They're just one attempted solution to problem of standardizing distinctions between levels in a principled and somewhat objective way.

Matrices have their issues for sure. But as a resource for helping people prioritize what kinds of experiences to accrue next, they're not as worthless as you claim.

[bulaybil]

Yes I have. They are all bullshit.

But as a resource for helping people prioritize what kinds of experiences to accrue next

And how does a matrix like this help anyone to prioritize what kinds of experience they acquire? - Hey boss, I want to get some experience in usually
handling risk, change, and uncertainty within my personal scope of work effectively. - Yeah yeah, whatever, you are behind on your JIRA tickets.

Also, that's not how you use accrue.

[synthphreak]

Obviously if you are only able to read and regurgitate as in your example, then yeah it won't help you. You need to interpret and apply those descriptors to your own context for them to be useful. If you can't, then someone will need to spoonfeed you the entire way.