Thank you! We were hesitant to use QR codes because there is so much friction with its usage. But I love the augmented reality idea, using T-shirts would be a feasible way to make AR interactions work.
I didn't know about NewBase60, so we only allow lowercase and numeric characters, and we picked a font where 0 is distinctly different. NewBase60 looks like a much better alternative, I'll look into it. Thanks :)
Wow, thanks for this :) This is exactly what we thought when we came up with the idea. These are great suggestions. We thought about the benefits at conferences but never thought of couple shirts or shirts referencing other shirts. There’s definitely room for creativity in this area. Thanks again!
Thanks for taking the time. Logo in a QR code looks really cool. We decided to leave shorter codes for later but when we do open them, I'll reserve 1337 for you :)
I’ll fix the home link right away and add a privacy policy. Thanks again!
It's mind boggling that they pay as much as $2 per install but can't afford decent design. I've never seen a good looking toolbar, it's as if they try to make them ugly.
I made Number March while learning Swift. In Number March, you defend against waves of marching numbers. Numbers are divided by towers. You create towers and increase their value in strategic places in order to divide passing numbers until they disappear. The game is a combination of action, tower defense and math. Hope you enjoy it!
It's indeed very helpful. Predictions should be independent for wisdom of the crowd to actually work. But we did introduce this dependency by revealing crowd predictions after yours as a tradeoff. We want to give feedback on how our users are doing, so that they're incentivized to continue making predictions.
Sometimes what you see as crowd prediction could be just a couple predictions. As new predictions come in, we adjust individual scores. We are planning to hide scores until a healthy number of predictions are made on that profile. That should help a bit on the dependency issue. We are open to suggestions as well. Thanks for the feedback.
Glassdoor indeed skews low and gives you a wide range. There are other sources: salary.com, payscale.com and also my own startup https://salaryfairy.com
Instead of giving the market price for a company/job title, we aim to give a market price for your own background and skills.
One interesting finding was that not only SF salaries are much higher compared to rest of the US, but users from SF tend to over-estimate how much the rest of the country is making. You can see this effect in the third map at https://salaryfairy.com/blog/first-10k-users-salary-maps-and...
I assume once they register your credit card number with the card provider, they have no longer any use for it. The connection between your card number and your apple id can be stored on the card provider side.
When we were first starting out, the feedback from our initial show HN post tremendously helped us shape Salary Fairy. We want to show you how much it has changed over the last few months and hopefully get more of your feedback.
I tested the page on Opera 12 for Mac and Windows 8, but couldn't reproduce the issue. Which OS do you use? Could you also let me know the exact version number of Opera 12. Thanks!
Thanks :) We have an opt-in program called FairPay, where we connect our users with employers who are willing to pay at least the crowd predicted salary. We charge employers to schedule phone calls with candidates.
Thanks, that's a really good point. Right now we bring profiles based on factors such as their score, location, and profile similarity. But the number of predictions they received so far is not one of them. We'll make sure to take it into account as well. Thanks for the feedback!
Yes, the charts are US only. Averages are quite skewed. We have CTOs at 2 person startups as well. One of the things we learned is that averages are not very good for comparing your salary. You need to look at other data points for it to make sense (e.g. number of employees in the company, years of experience, etc.). That particular chart is good for comparing top paid job titles with each other, not so helpful to get an idea how much you would make.
Hi HN! We built these visualizations with d3 library. I'd love to hear your feedback, especially on the visualization of predictions between cities. Thanks!
It does factor in location for regular profiles. Normally, people in the same city and field make predictions for Salary Fairy profiles. For fictional characters though, we relaxed that limitation.
Salary Fairy predictions let you know how much you are worth in the job market. Even though the family is always broke, if Michael decided to leave, that's how much he could make in another company :)
Thanks for the feedback. The header is important for user experience. We noticed that most users go directly to the header to find out more about the site. And having it always visible makes the site more usable. I can understand how it can become a pet peeve, but I think it is a good tradeoff between usability and screen real estate.