First paragraph intro is helpful for understanding if you want to bother opening the PDF:
What this paper is about and for whom it is written.
In this paper, we try to explain that mathematics as a scientific discipline enters the period of crisis. In plain words, research level mathematics is becoming too complex for human comprehension. This has serious implications for mathematics education, and our paper is written for everyone who cares about it.
I relate to your story, I definitely got to be that self-centered twenty-something for a good long time. Would love to be able to call my dad right now.
This seems likely to be the case. Perhaps there is a way to design a test such that it measures how quickly one can become capable in some informal "programming language" designed specifically for said test?
Imagine an interview where the interviewer is figuring out an area where the candidate is missing some knowledge, then the interviewer goes through and helps them learn that knowledge. Concrete example might be candidate has zero experience with vuejs, so interviewer works with them to build a vuejs prototype.
Scrum is being applied like a shiny new hammer to everything that might have seen or heard of nail a once.
The primary reason scrum should be used for software development is when iterating closely with a knowledgeable customer. The pattern basically outsources the discovery of what to build onto the customer - and if the customer can tell what good looks like, shazam! scrum is downright magical!
Guess what, most software teams are isolated from the customer, or the customer/product owner doesn't know what good looks like, so no wonder scrum is getting a bad name as teams struggle to get value out of scrum activities.
There is a reason why teams need to have flexibility to modify their R&D patterns and processes. Without that flexibility you get to do scrum and the results make you wonder if you are doing it wrong.
