Hi all,<p>I made this site for the situation where you and your colleagues are all at lunch and the discussion of salary comes up. While a lot of people don't feel comfortable discussing specific numbers, they're all still curious :) So this site lets someone start a 'secret' with just a few clicks (no registration etc.). That 'secret' has a code that other people can enter on the site, too, and then by telling the site your salary it will show everyone on that secret the minimum, maximum and average salaries.<p>As per the 'privacy' page, I'm not storing any personal information... it is anonymous.<p>It was also a good chance for me to learn Silex (the PHP "micro-framework") and Twitter Bootstrap (though not so well), practice 'progressive enhancements' with Javascript and play with PaaS via Openshift.<p>Anyway, thanks for any feedback, flames or criticisms...
Say I wanted to know your salary. I could start a secret and enter the minimum minus one before I send you the link.<p>Is there a way to prevent this sort of scenario while letting the service remain anonymous?
I started a "secret" here (for up to 25 of us) to give this thing a test drive:<p><a href="http://www.salarysecret.com/continue/36-teputo13" rel="nofollow">http://www.salarysecret.com/continue/36-teputo13</a>
Great idea. Why not make the code easier? Start with three letter dictionary words, then four, so on till about eight. Then restart with non-dictionary.<p>Now regarding knowing friend's salaries; From personal experience I can now say that it is not a good thing. I come from a culture where salary is not well kept secret and you usually know your friend's. This leads to a constant state of discontent unless a] You are on the top b] you are the type of person that can factor in intangibles well (hint: most people are not).<p>You might be working on a really good project, but the next day you arrive at work you will sit there sipping coffee and thinking how come my buddy is earning double working on a iFart app?
One of the main issues I see with this is that people lie.<p>They lie so much, that almost everyone in HR completely discounts employee based salary data. Instead, if they need to understand what a market rate is for a salary, they ask <i>employers</i> what they are paying, since to them it is just another expense.<p>Talk to anyone worth anything in HR and they will echo exactly what I said. You may as well guess what your buddy is being paid, because whatever they tell you is never going to be accurate enough to provide you with an informed opinion.
This is a neat idea. I like that you didn't choose to implement another todo list in order to experiment with a new framework.<p>I think the wording of "continue a secret" is a little confusing. I appreciate the brevity but maybe "participate in a secret" would be more accurate. "Share a secret" sounds nice -- because that's what we do with secrets :-) But, it might get confused with the sharing of that particular secret code instead.<p>On a UI note, having to click on the help icon to dismiss the pop-up was a little annoying.
Cool idea. I'm wondering if there's a way to implement this system without having to rely on trusting the server with your data. Homomorphic encryption seems like it could be useful in this context, since the data is small.
good idea to help people gauge how well (or not) they're doing salary wise.<p>is there a control to prevent too few minimum participants, which would make it more obvious whose numbers are whose?<p>the interface could be more graphical, less text heavy.