You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just completed the State of CSS 2024 survey, and I was presented with this:
It says that I am in the "top 100%". I expected I'd be. 😅
I assume that number is incorrectly calculated, as it indicates that all participants have a score that high or higher. And I truly believe there are at least a few participants so far that don't know about at least one feature.
Though even when the number is correct (e.g. due to being the first participant or all other participants scoring higher), the hint shouldn't be displayed if the number is 100%. Maybe it should only be displayed if you're above average.
Or there could even be different hints for different scores, encouraging low-scoring participants to read more about the features and congratulating high-scoring ones.
Sebastian
The text was updated successfully, but these errors were encountered:
Yeah, I think we'll end up scrapping the whole system because calculating that percentage requires running costly (and evidently, wrong) db queries every time.
I just completed the State of CSS 2024 survey, and I was presented with this:
It says that I am in the "top 100%". I expected I'd be. 😅
I assume that number is incorrectly calculated, as it indicates that all participants have a score that high or higher. And I truly believe there are at least a few participants so far that don't know about at least one feature.
Though even when the number is correct (e.g. due to being the first participant or all other participants scoring higher), the hint shouldn't be displayed if the number is 100%. Maybe it should only be displayed if you're above average.
Or there could even be different hints for different scores, encouraging low-scoring participants to read more about the features and congratulating high-scoring ones.
Sebastian
The text was updated successfully, but these errors were encountered: