I think we are in agreement, but if we try to play devil's advocate to ourselves :)
There are tasks you can conceivably determine some thresholds:
You pick up 10 bushels of apples a day, you "meet expectations". You pick up 15, you "Exceed expectations". You pick up 5, you "need to improve".
But again, I will make an argument that these are curved as well, it's just that curving was done previously and on large data sets.
You can establish seemingly absolute criteria in software - from seemingly hard numbers (line of code, programs deployed, tickets closed, IRs in prod after deployment, etc) to softer numbers (are your comments good, is your code maintainable, etc). But again... how do you come up with these numbers? Either you make them up, in which case they'll have to be adjusted based on reality of your actual developers, or they're based on previous experience, in which case it's the reality and curve of previous developers.