I don't know the actual numbers, but it's been pointed out that at any given time something like half of all programmers have been doing it less than five years, for decades now.
That, plus the strident ignorance of past art and practice, seem to me to bring on a lot of issues.
They then went on to list the errors that this brand new entry level employee had made when writing ... an authentication system ...
I was more than a little shocked when I realized they were serious and hadn't realized the issue was sending the new entry level guy to do that job alone.
I've always seen authn. Where'd you pick this usage up?
For my part, I have not encountered "authn", "authz", or "authk" before. But prior discussion did not even mention the word "authorization", and that seemed worth bringing out in the open.
So, not nonresponsive, just responsive to things you weren't personally interested in.
They way I see it is that it was a case of something that wasn't working, then replaced with something that was working.
I don't know what your metrics about "good" or "bad" are but eventually they got a solution that covered their use cases and the solution was good enough for stakeholders and that is "good".
that is an excellent term.
Maybe a bit of both.
^H^H^H^H^Hitic
There, FTFY.
I could have jumped on it and played it but I figured just another toy craze, it'll be over before long.
With yes the added confounding factors of how often our industry seems to prefer to hire youth over experience, and subsequently how often experience "drains" to other fields/management roles/"dark matter".
The narrative should lead to the conclusion. If I told you the story of the tortoise and the hare in which the hare gets shot by a hunter, then said the moral is "perseverance wins", you'd be rightfully confused.