▲ | contagiousflow 3 days ago | |||||||||||||||||||||||||
Let me make a comparison. If your manager says your performance is based on lines of code, you will be incentivized to write lots and lots of code. Does lots and lots of code mean you are being productive and making good software? Sometimes yes! Sometimes heaps of code means you are being ultraproductive and making amazing software. It could also mean you are writing much more code than you need to, introducing new bugs, not thinking about generalizing patterns, creating technical debt, making a worse UX, all of which I'm guessing you would agree are important to software engineering. But none of those things are going to matter in the lines of code metric. So yes, sometimes having metrics for performance are worse than imperfect. Sometimes they are antithetical to the supposed goals. Student time is a zero sum game, and having a large portion of a crucial time in their development spent cramming for one metric is not going to have good outcomes for a society, only good outcomes for a metric. | ||||||||||||||||||||||||||
▲ | ACCount37 2 days ago | parent [-] | |||||||||||||||||||||||||
The optimal amount of "teaching the students the actual subjects" you need to do to have them get good SAT scores is significantly higher than zero. Sure, you can cram for SAT, and you can get gains on the metric from that. But you can't just cram all the answers into the students and have them get a perfect score via rote memorization. Students still have to learn things to be able to do well. Which is why SAT beats the "performance is based on lines of code" tier of shitty hilariously gameable metrics. | ||||||||||||||||||||||||||
|