Had a gig like this, the codebase was so shit it took days to do simple stuff, it was highly domain specific logic I cared nothing about and I was going to leave ASAP.
Most of the time l bulshited my way through turns out a lot of the features got scrapped because they weren't necessary in the first place (ie. there was another way to do it for eg. or client didn't really need it), requirements got updated that would have made any progress I did worthless,etc. There were two crunch weeks before releases where I did some OT to help push stuff out the door (wasn't even my backlog) other than that yeah - did two months of work in 6 months I was there.
In the real world, someone who is 4-8X more productive than their peers is also significantly more senior and therefore paid significantly more. You don't see seasoned experts on the same teams as inexperienced juniors all getting paid the same.
In my experience, the best team cohesion happens when everyone is putting in similar amounts of effort.
What if the seasonal expert is the 5 minutes work person, and the juniors the 5 hour work people (yeah, I said 4 hours because I don't believe any developer can output 6+ hours per day consistently)
On the other hand, as a seasoned expert, I sometimes solve an issue in 5 minutes which took a junior a day to still not figure it out.
I think 15 years would do, to be named a such.
I guess you end up in a 5 minute job when your work is really boring.
> You don't see seasoned experts on the same teams as inexperienced juniors all getting paid the same.
But don't you? There are tons of accounts now of juniors joining and getting inflation adjusted salaries, and a loyal old dog discovering that his 'high salary' is actually just a smidgen above what this new young buck is getting
> There are literally days in which the only time I spend on my job is the few minutes it takes to attend the morning stand-up. Then I successfully bullshit my way through our next stand-up to hide my lack of production.
At that point, it's not about grinding harder or going above and beyond. This is a problem of misleading everyone around you.
It's not just the company that suffers. These situations usually result in the rest of the team having to pick up the slack to get things done. The person doing little to no work is taking advantage of their peers' productivity.