zlacker

>>todsac+(OP)
Much of CBF can be explain simply through rewards and incentives.

See, when I joined my current company, I was full of energy and I did BF. I fixed broken builds. I made our abandoned test suite green. I refactored our deployment pipeline. I hunted down the root cause of bugs and fixed them. But then I noticed several things.

First, rather than encourage people to behave like me by example, they did the opposite. Why fix a broken build when I would come along and do it? it turns out doing shit work just gives you more shit work.

Also the guy does hack jobs got promoted ahead of me because he is a master of optics and presents his work much better than it is. And look at how fast he delivers! it doesn't matter his code keeps causing problems in prod, by then he has moved on to another project and it's someone else's problem.

Oh, and that junior guy than I spend several hours a week helping makes more than me, because we hired him in 2022 when we were desperately throwing money at people, but I didn't get a raise in 2023 despite an "exceeds" rating because you know, it's tough times and we need to buckle up.

Listen, I love what I do and I want to excel at it, but is it any wonder and CBF? At the end of the day I work for a salary. If my efforts aren't rewarded, or sometimes actively punished, my motivation goes down the drain. Sure, part of it we do for ourselves, but at some point you have to question who is really benefiting from the situation.

>>angarg+j62
When we only work for a salary we’ve lost sight of what it means to be alive. Move on, go somewhere you deserve to be. Find your people.

>>RHSman+G72
Let me ask you something honestly, where do you find your people? Is there really such a place that operates differently? I find myself in a very similar situation as the GP, but I agree with your sentiment, so I would prefer to taks your advice. In my experience, every work place has the exact same problems as they described. I just want to know whether there are indeed better options, and what to do to find them.

>>epups+Kk2
One option is to work at a place with longer development horizons and where the top priority isn't getting the latest feature into production by end of day Friday. Research institutes and R&D departments at huge companies (possibly even companies outside the software engineering sphere) for example operate very differently than companies/departments that directly ship software. Of course these places have other problems and they may not necessarily be 'better', but it is at least they are different problems in my experience, and personally I've found them preferable.

>>dagw+Ds2
Getting into these I found pretty difficult for many reasons, and usually you take a significant pay cut.