Hacker Timesnew | past | comments | ask | show | jobs | submitlogin

Not useless to me. While more preprocessing would be welcome you can easily distinguish annual, daily, hourly compensation yourself.


No you can’t. A day wage can be hourly for some. The table shows a mix of values that are meaningless.


What values could reasonably be both an annual salary and an hourly wage in the US, where this data is from? While of course mixing annual and hourly is bad practice and makes sorting pretty useless, it shouldn’t be difficult to distinguish the two if one is so inclined. I imagine there’s a very clear gap in that sorted sequence where the hourly values transition to annual. Take 20,000. As an annual salary you’d be living in poverty, and as an “hourly wage” you’d be making over $40,000,000 annually. No one making that much is actually paid an hourly wage of $20,000.


If I sort. Atleast on mobile. How do I figure out the lowest annual salary? I can’t. I don’t understand how anyone can defend this data. Either collect and provide good data or don’t bother at all.


I’m not defending the data. I’m pointing out that it could be processed without much difficulty to clean it up, if so desired.


Then you can just look at the annual ones. Anything over 75k is more than safe to say is annual. I only go that high because it seems like you need certainty that it is not quarterly or bi-annual.




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: