One thing society needs to get right is not screwing over slow thinkers from day 1. A slow thinker can sometimes generate amazing projects over remarkably short timelines, but deliver "meh" performances on standardized tests that use time pressure to fit scores to a bell curve
-
Show this thread
-
I think a lot of people just assume that human populations somehow fit a bell curve neatly over various traits, but many of these tests are *designed* to clean up the curve by tweaking test items until beta populations fall along the right line
1 reply 3 retweets 47 likesShow this thread -
This might mean adding redundant "easy" questions to push more low-scorers up to the middle or using time pressure to push slower readers/thinkers down to the middle, depending on how the curve looks on initial tests. Or vice versa.
3 replies 0 retweets 34 likesShow this thread -
Replying to @webdevMason
This might be a bit uncharitable. Psychometricians are looking for items with a range of difficulties that can discriminate at different levels of ability. If the distribution ends up being really right-skewed, it means your test can't tell people apart at low ability levels.
2 replies 0 retweets 0 likes -
Replying to @davidklaing @webdevMason
Conversely, if the distribution is really left-skewed, then your test is probably too easy, and you're not discriminating at high levels of ability. Time pressure is one way to push that needle, but often they really do just come up with harder questions.
1 reply 0 retweets 0 likes -
Replying to @davidklaing @webdevMason
For all the problems with standardized tests, I don't think it's because the people who make them are blindly trying to match their tests to a normal distribution just because it looks pretty. The problem of time pressure in particular is usually just about resources.
1 reply 0 retweets 0 likes -
Replying to @davidklaing
They literally *are* doing this, but not because it looks pretty — fitting people to very clean standard deviation slices makes it really easy for the folks who use the scores to e.g. evaluate applicants to narrow their pools quickly
1 reply 0 retweets 0 likes -
Replying to @webdevMason
Agreed! But isn't that what you would want? Imagine you're a recruiter at a huge company and you're trying to narrow down a pool of 1000 applicants to the best 100. Don't you want a test that discriminates well at all levels of the actual distribution of ability?
1 reply 0 retweets 0 likes
If the thing you're testing for *and* speed are two very important traits for candidates, sure. But if speed isn't that important and there are many other traits that matter more, you might eliminate many candidates who are stronger in those areas unless you understand the tests
-
-
Replying to @webdevMason @davidklaing
In other words, scores might be a decent tie-breaker while being a very bad early filter
1 reply 0 retweets 0 likes -
Replying to @webdevMason
That's a good framing. Part of the problem is that many examinees have no interest in doing day-long projects for every opportunity they apply for. As for me: slow thinking all the way.
1 reply 0 retweets 0 likes - Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.