So that's why we suffer enshitification.
Those who succumb to the Socio-Economic and climb it so.
"Upwards mobility".
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
So that's why we suffer enshitification.
Those who succumb to the Socio-Economic and climb it so.
"Upwards mobility".
I am so tired of worse products in the name of upgraded products that are literally worse in every way but a bunch of buzzwords and in groups bragging at the top while not knowing anything at all about programs or even the product at all but just seem to be there because they drink with the CTO.
Ugh. The twiddling thumb era of trying to look busy by dismantling the old machines for parts.
I say this is only ok because he did that in amazon. Fuck amazon
If he did that in a medium-or-less sized company that would be a really shitty move.
The problem is the large companies like Amazon buy all the small ones and put these people in charge lol
In a small company noone would try to label you "l5" or "l6" and probably an actual human would make your comp decision. You take the byzantine incentive structure away and people just try to do a good job.
Well at least harming Amazon is a net good
Imagine getting paid to do it.
Was in this position at Microsoft for two years. I already hated them because I ended up working for them after they acquired my smaller company. Pennies on the dollar, massive layoffs beforehand, fired literally all the most important people (which is why I wasn't fired, I really am just trying to collect a paycheck and do nothing more).
Anyway, ended up basically being placed in a middleman position that I quickly realized didn't need to exist. Basically, spent two years slowing down communication between my companies team and the existing Microsoft team. Literally, I just kept the two teams from directly communicating and going through me for everything. I think I wrote less than 1000 lines of code during that time.
And no, I didn't like my team either from the original company. They were all new hires prior to us being acquired and they fired everyone on my team that had worked on the project for nearly 5 years. So, didn't feel bad about slowing them down either.
Basically a shitty startup that milked it's employees with hopes of Microsoft becoming our customer. Encouraging people to exercise their options only to sell the company for pennies on the dollar and fire them.
Got through two years of slowing down an awful genocide supporting company before the layoffs finally got me.
Was a good run.
And this is why you rarely find decent people with good income in todays economy.
You write clean code and you get replaced in 2 months, because everyone can work on that code.
You write an unreadable mess that no raise will convince other employees to work on and suddenly your holiday requests don't get declined anymore.
These days it's also because you want the AI to get confused by your code too. If it's too clean you'll have a PM with cursor making PRs wondering why your salary is justified.
I fought for getting a 4/5 rating at an old job and gave lots of examples. Their argument was that I didn't deserve it because those were just expected. I pointed out my work compared to others in my team and was told that it compares across the company, not the team. I kept causing a fuss about it because I was so angry about it and finally my manager said something about the bonuses has already been communicated and people would be angry to get less. I was confused because I didn't want more money, I was just offended they said I was performing on average when I was going above and beyond every day. It was also really embarrassing to me. If they'd just said the rating doesn't affect anything except your bonus I wouldn't have even cared.
The whole thing is all BS.
At one job, my manager had a spreadsheet that he was tapping away at during my review. He had the audacity to tell me that he had to downgrade some things so that he wouldn't have to go to a committee to defend at the individual or group level.
I transferred to a different product.
finally my manager said something about the bonuses has already been communicated and people would be angry to get less
That's because they have a fixed budget and the proportions are tied to evaluated performance tiers, increasing your rating would contractually require them to compensate you more from the same pool of money
You're falling for the "we've constructed this machine to tell you no so you can't argue with us" ploy
No, as I said to another, upper management has every opportunity to fix the budget. Your direct manager however can not
I've found that laughing in their faces and putting in 2 weeks is fairly effective at breaking that wall. Amazing what money they can find when faced with the alternative. Otherwise, the correct move is to actually leave. All of you cowards that submit to the machine make it worse for everyone.
And I have in fact left that kind of jobs myself. Not trivial in a job market like this one though.
Need to make unions stronger again.
The whole thing is pegging my BS meter, including letting an L5 deploy without a code and architecture review, TC, and the fact that they're posting this and claiming they're still there.

Yeah this was my experience when I worked there. Driving goals and doing good work isn’t enough. You need a fancy project to demonstrate “expanded scope” otherwise your promo would get rejected.
Sometimes things worked the way you wanted and people got promoted doing their normal job. A lot of times though there were a lot of fancy projects built to get people promos that suckers got stuck with the bill on.
This ain’t a case of one dude scamming the system as much as it is institutional rot from red tape.
Its pretty well known that "lines of code" is a horrible metric to judge programmers with. It seems "number of new projects" is pretty similar, though at a higher level of abstraction.
Unfortunately that metric is applied to a lot more than just programmers; and I think getting rid of it would involve completely restructuring the type of activity our society is oriented around, and would run up against the life philosophy of the people in charge.
Of course I'm not against progress, but I'm talking about executives that don't plan beyond the next quarter, politicians that don't plan beyond the next election cycle, the endless pursuit of growth, and the inability of market economies to cope with the fact that sometimes inaction is more advantagous than action. All of this encourages endlessly churning out 'new' things, without designing those things to last or putting in the effort to maintain them.
I apologize for bashing Java so hard in the past. I wish everyone wrote everything in Java these days. Digital life would be so much better.
You owe royalties
Yeah, Oracle licencing has really taken the shine off Java and relegated it to the legacy dust bin.
Sounds like whoever decides these things knows nothing about IT.
they don't. I mean for example Amazon puts all new hires on "on call" status for like a week every month. the LAST people I would want working On Call and waking up at 2am to try and solve something are fresh grad hires. You can actually watch videos on youtube of new grad amazon hires doing this, they actually document themselves, and the vast majority of them are "well it's 1am and I just got a call...I'm going to try and fix this ticket but really I have no idea what I'm doing" annnnnd generally nothing gets fixed or they break it worse. So they end up being sleep deprived, going into the office the next day and sleeping at whatever workstation they can find available and it leaves you wondering "what's the point?"
I personally am of the belief that being on call for stuff like this is pointless when you're world wide and could literally just transition the stuff to a different team in some other part of the world but I guess Amazon treats it as a sort of initiation process or whatever.
Sounds about right. There is no longer any incentive to focus on maintenance and incremental improvement (the stuff that actually keeps the lights on and the revenue flowing). It's all about the new and shiny--even when it results in regression.
You get the behavior your incentives encourage, whether you realize what those behaviors are or not.
[ In lieu of a comment, please see "Bullshit Jobs", by David Graeber, which is incorporated here by reference. ]
Something I find cool about this book is that it's so well known that people who haven't even read it will often gesture towards it to make a point. It reminds me of how "enshittification" caught on because so many people were glad to have a word for what they'd been experiencing.
It's a useful phrase to have. Recently a friend was lamenting that they'd had a string of bad jobs, and they were struggling to articulate what it was that they wanted from a job. They were at risk of blaming themselves for the fact that they'd struggled to find anything that wasn't soul sucking, because they were beginning to doubt whether finding a fulfilling job was even possible.
They were grasping at straws trying to explain what would make them feel fulfilled, and I cut in to say "all of this is basically just saying you don't care what job you have, as long as it's a non-bullshit job". They pondered it for a moment before emphatically agreeing with me. It was entertaining to see their entire demeanour change so quickly: from being demoralised and shrinking to being defiant and righteously angry at the fucked up world that turns good jobs into bullshit. Having vocabulary to describe your experiences can be pretty magical sometimes
What's L5 and L6? What's TC?
L5 and L6 is a label for career progression, like getting promoted from staff to senior, just with different words. TC is total compensation.
Yep, this is the culture I keep running head first into as I try to level up my career.
The one thing which COULD justify it, is technical debt. A programming language not supported anymore or in short-term/mid-term, bus factor, too much knowledge transfer, etc. But yeah, lots of times it's "business as usual" just for "progress" and fancy buzzwords.
Golang is technical debt in language form. A language that gained limited and now sagging popularity, for good reason. I hate to work in Java but hate golang more. It's the lightsaber of programming languages. I've got shit to do give me blasters and all the rest and I don't want to wank myelf off about how I did it all with channels.
Is that why they are gradually replacing the bad AWS Console UI with something 10x worse?
Apart from being slow, having discoverability issues, not being able combine filters and actions so that you frequently need to fall back to shell scripts for basic functionality, it being a complete PITA to compare things between accounts / regions, advanced functionality requiring you to directly edit JSON files, things randomly failing and the error message being carefully hidden away, the poor audit trail functionality to see who-changed-what, and the fact that putting anything complex together means spinning so many plates that Terraform'ing all your infrastructure looks like the easy way; I'll have you know there's nothing wrong with the AWS Console UI.
Perverse incentives combined with underskilled management 😐
Flawless victory.
Not really. That's just how it works at mega tech corporations. He should try working for a startup.
This almost makes me appreciate my current job, where most stuff has been in place for years and any changes take forever.
It's kind of a bummer that it's going to take like six months to add a linter, and they only started using git like last year.