Programmer Humor

Imagine getting paid to do 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.

Technical people don’t understand the business, you see.

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.

L5 and L6 is a label for career progression, like getting promoted from staff to senior, just with different words. TC is total compensation.

Career levels at Amazon (basically pay grades)
Total Compensation

At Amazon you have the following levels

L4 - Junior. A new grad. Expected to be promoted within 2 years or let go

L5 - Mid engineer. Very wide band. Encapsulates anything between a level 2 engineer and a team lead at other companies. Can be expected to lead individual teams at times. Is considered a “terminal” position (there’s no expectation of a promotion past here)

L6 - Senior. Has the scope of what a Staff engineer would at other companies where you’re not only concerned with your team but others in the department. I think like 10% of engineers ever hit L6

L7 - Principal Engineer. You have like 1-2 of these per department. These are more like architects at other companies. About 1-2% of engineers ever hit this band.

L8 and beyond are for fancy hires and shit. Very few if anyone ever works their way up to those bands.

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.

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

Same. Generally speaking our company is pretty healthy, but we're still stuck in this really stupid leveling system where advancement is tied to greenfield development and I've been doing maintenance and compliance work for the last five years.

Man, it's so frustrating. I just can't turn off my own qualms with shitty corporate culture and it means I will be less successful by the metrics we've set ourselves.

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

I worked in a heavily regulated industry. Everything required a manual test. Let's say you have an employee ID that is 10 digits long which they use to log in. You had to have some else (couldn't be the developer) to write a series of tests, get those tests approved by 5 people(with specific titles) then a third person to execute the test, then the second person had to write a report saying it all passed, then that report had to be approved by the same 5 people.

That typically wasn't the delay. The delay was to execute the tests we needed to stop production. That typically was a 6 week wait(unless urgent for "reasons") and changes like "I will drop scrap by 83%" was typically told wait till July 4th or Christmas breaks. Why? Because production would be down for 3-4 days typically. Someone had to start the system, ok no entry produces error, executor and developer have to sign a physical paper, restart the whole system, now an entry of 1 digit produces an error, sign the form, repeat for all digit quantities up to 9, repeat for all digit quantities up to the choosen value(based on severity if an issue occurred), 2 people sign for each one, system restarted between each. If you had say an enter button and a cancel button each had to be checked for each quantities of digits. Oh but wait what if someone just types there name... Now repeat everything for alphabet values... What if someone does combination, more tests, more restarts, more signing.

Reports easily surpassed 1000 pages, no one really had time to check all that so I saw so many missed signatures and missed tests. I asked the "senior validation expert" can I just automate a lot of these tests using unit tests and attach a computer generated report of all tests passing and the source code of the tests? " the response I got was" what's a unit test? "they still don't use any of them to my knowledge.

The fact they had to do this to earn a promotion is an institutional problem. Don’t hate the player, hate the game.