this post was submitted on 11 Feb 2024
64 points (100.0% liked)

Technology

37720 readers
338 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
 

Found via https://yorickpeterse.com/articles/what-it-was-like-working-for-gitlab/

I always considered the gitlab model, where the comp can be calculated via a public online tool, to be pretty progressive.

While this certainly doesn't scale (as they admit) I think the sentiment is right.

you are viewing a single comment's thread
view the rest of the comments
[–] frog@beehaw.org 3 points 9 months ago

Agreed with this. Even if one leaves the high performers out of the equation, if someone is consistently shirking work, and others are having to pick up the slack in order to make sure deadlines are met or that quality standards are reached, then that's a recipe for resentment if pay is the same. I don't think everybody on the team has to put in exactly the same level of work, and in a good working environment people tend to be pretty understanding of variances in output (both quality and quantity) as long as everybody is trying their best. Unless you've got someone that does significantly less than everyone else. To deal with that, you either need to have really good management, or pay rates need to reflect the actual work done.