I’ve used best industry practices for such web apps, and I’m curious what do you think these concerns are!
314 karma · joined October 11, 2014
I’ve used best industry practices for such web apps, and I’m curious what do you think these concerns are!
I also detest these popups and "usual" customization pages.
If you think I can improve it even more, please tell me! :)
Where are such jokes? How even is that topic here?
I’m confused.
SPOILER: asymmetric encryption with private/public keys.
You don’t provide LinkedIn credentials in any way to me or to my website. You use it to authorize with LinkedIn (similar way, you can authorize with Facebook, Github, Google, Twitter, and other OAuth platforms).
The only thing that my website can read (and for very limited amount of time):
- Your email address, - First name and last name, - Unique LinkedIn ID, - LinkedIn profile photo URL.
That is it. There is no write permission for anything. This authentication token doesn’t allow anyone to log in into your LinkedIn account.
This type of technology is called an Authentication Provider, and is used to authenticate you on my website (not on LinkedIn).
Here you can read exactly how I process the data mentioned above: https://www.fellowage.io/privacy#linkedin-profile-data
In fact, the requirements are quite relaxed already. I wanted to make it even more strict, but my partner insisted on relaxing them.
The age of simple passwords are long gone, as they are really easy to crack with enough budget.
Have you considered a password manager that can generate random unique and strong passwords for each website (and store them securely) for you?
- For the data question, you can find all the information on our privacy policy in details (https://www.fellowage.io/privacy): what is stored, how it’s processed and for what reason, lawful basis, etc. Please read this about how I disassociate account information (and protect it) from raw pseudo-anonymized wage entries (that are already "public"—available to all users of the system via search): https://dev.to/foundsiders/how-have-i-ensured-the-privacy-an...
- I don’t provide these features right now. Currently, product solves slightly different problem, and I think it’s possible to expand its feature set to cover for search by job title/location, or company. You can already search by company/location though. (It’s a search bar at the top of the webapp’s UI).
- These are all features that show you statistical distributions, and while they are useful, there are plenty of tools that solve for that problem already. I set out to solve slightly different problem: “Who should I look up to in my company to earn more?” or “How up-to-date are specific salary entries?”
- I plan to notify my users to update their entries every half a year. Also, there are features that allow users to set up alerts for certain companies/locations/job-titles when there are new entries, or updates. These alerts are aggregated in a weekly report (if it’s not empty, of course).
- The current plan for monetization: there are two types of accounts: free and paid. Free account can view their own company/location without limitations, and for viewing of other companies/locations there are 3 monthly free views, that can be substantially and permanently boosted with referrals (similar to what Dropbox did with their referrals). Paid account has no limitations, of course.
Please tell me what you think about these replies! :)
On the other hand, it’s not provable (I don’t save the exact number, and I separate the account and wage entry securely so that the user and only user can realize that connection: https://dev.to/foundsiders/how-have-i-ensured-the-privacy-an...).
If I apply replace entries with statistical ranges, then the product would become a clone of other products for this (like Glasdoor, LinkedIn Salary, etc.). And it won’t solve the problems I set out to solve with it anymore.
2. By requiring users to share their wage information at signup. The idea is that to see salaries of others you need to share yours first. It’s possible to delete wage entry later, but also that makes the user lose access to others, until they either: add wage entry again or upgrade to paid account plan.
3. Yes, I agree that certain folks will have no motivation to share, because they don’t care to know what others ("below" their level) earn. What could be interesting for them is what others of the same or similar level earn. So maybe something like peer-to-peer sharing may be interesting to these folk.
4. We’re going to implement an algorithm that will try to detect "suspicious" data entries, and devise some a more advanced validation mechanism. Such entries will be hidden from other users in the meantime.
So there are two fields: core wage (this is what you get no matter what), and other benefits estimate (here you just bundle everything else, and for non-deterministic stuff, make your best estimate, of what it’s worth).
"More than 50% come from bonus or stock, or others" is actually not quite true in every culture or country. For what I’ve seen here in Germany and in few other countries, 90% or even more is the base salary.
About currency: It works, when you type the currency, you need to select the entry from the auto-complete. I’m thinking about making it select the currency automatically if only one option matches.
e.g., “Who should I look up to in my company to earn more?” or “How up-to-date are specific salary entries?”
My product doesn’t answer the first question just yet, but it will in the future via a peer-to-peer sharing feature that I’m planning in the next version.
I have always felt certain anxiety when thinking about my salary and only guessing what my colleagues might be earning. This issue is especially problematic in cultures and countries in which talking about wage numbers is an unspoken taboo among the employees.
Quite often, the questions like “Should I ask for a raise?, or am I already earning maximum that my employer can handle?” “Am I earning too much for the work that I do?, or am I underpaid?” “Who should I look up to and learn what they are doing to get a higher salary?” have plagued my mind.
# Existing solutions:
Of course, there are services where you can look at salary levels or statistical distributions of wages. The problem with them is that they don’t give you specific (albeit anonymized) numbers of what individuals earn, and they don’t satisfy nagging feelings of fear and anxiety that I have mentioned above. Also, it’s hard to tell whether the numbers are up-to-date or not.
# The solution:
I designed this product to be privacy-first so that many more users feel comfortable sharing their wage information and keeping it up-to-date. It allows users to see all salary entries in their current company, search for other companies in preparation for negotiations. Here is the full list of features:
- I verify the data with LinkedIn profiles
- I nudge users to update their info twice a year
- I keep information quality high
- You keep your data anonymous
- You can see your and other companies data
- You can subscribe for updates for particular job titles/companies
# Plans for the next version:
I plan to allow users to share their non-anonymized information in an encrypted peer-to-peer fashion with each other if they want to. This answers the question like, “Oh, somebody earns twice as much as me… And has the same job title… Who is that?”
Tell me what you think about it! Is there something missing from your perspective?
The no-mouse challenge for a few hours makes you more proficient at using IDE without a mouse, and only keyboard.
Also, complex refactorings are so much faster in IDE, and I do refactor every 2-5 minutes as part of my TDD workflow, so IDE really makes me much more productive as I would otherwise be.
If you had to list things you have to stay up to date on, what that would be?
Which blogs and forums do you like to read?
Then, in one month of time, you can potentially have 5000$ or 5M$ in finances available.
In time though, in one month, you can have only one month.
It is true, it is spending your time. But it seems like this time is much more precious resource than money.
What do you think?
> number of new users acquired from shipping the feature
Oh, that is quite an interesting idea. If the author themselves acknowledges there is a problem—there should be a real problem.
Follow my thoughts (and please do poke holes in them!):
Financial debt allows you to deliver more -> sell more -> pay down debt quicker -> deliver more (if you got it right and haven’t failed).
So the money itself becomes a mechanism by which you deliver faster, and, as a result of faster delivery, earn more money to deliver even more and faster.
Now, the technical debt.
Earning more money from more feature delivered in current iteration might result in more revenue NOW. But does it result in more/faster delivery after that revenue happened?
Not really.
You can potentially hire more people. But they will only slow the team down at first. There is a delay between “more people” => “faster delivery.”
So financial debt can enable a positive reinforcing loop. Can technical debt do that?
While I have to agree that it takes the pain and struggle to understand some code out there, it is still worth doing, and a good indicator of the quality of the code, and the fact that it needs improvement.
Also, I believe leaving some “bad code” without understanding it, and just rewriting it, _might be_ unprofessional…
(Better refactor, of course)
Person A, a programmer, who writes easy-to-understand code, but takes a bit more time to finish their tasks
Person B, a programmer, who writes dirty code, but takes much less time to finish their tasks
The current non-technical manager will see only one part of the picture and promote Person B. Moreover, Person A might get in trouble, and pressure to “compromise on quality.”
Within a short-term, it is understandable.
Within a long-term, this is a disaster scenario!
So should the “code quality” be part of a performance portfolio of the developer when it gets to promotion time? And how do we get there?
Would you agree that we should think about specific issues that are slowing us down, and fix them one by one, starting from the worst ones?
(worst in sense of biggest slowdown/pain levels)