Ah, "Explaining". There's your problem.
Lets have a checklist with supporting documentation, please~
this post was submitted on 02 Aug 2024
317 points (97.0% liked)
Programmer Humor
32557 readers
136 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
My American self: Three WEEKS!?!?!!!?!!?
And believe it or not, we're still being exploited. Just not as badly as you guys are.
My 24 holidays are my 24 holidays, as long as I bill them 2 weeks (one sprint) on advance. Which part is exploited? (and also in what country, for legal reference)
I mostly mean the lack of proper universal healthcare that forces many workers in the us to use holidays for sick days. I was assuming that's the reason 3 weeks of holidays sounds outlandish to the original commenter.
I mean, it's also uncommon to actually get 15 holidays on your contract in the US
But how do people in your country get exploited, when they do get more holidays
We get underpaid and an unreasonable amount of money still flows to shareholders etc. Essentially we still suffer from all the exploitation that comes with capitalism.
Situations like this remind me of devs that talk at people, but not with them.
Leaving 3 weeks worth of senior work to a junior is your own damn fault.
The meme doesn't say that happened
Came back to learn you created job security
FIFY
Can't help but think of a "senior dev" "explaining" (hing: brain-dumping) some bizarre reasoning why his unusable untested undocumented untyped API uses floats for item counts or something, and expecting the "junior dev" to just nod and keep that in their mind and adapt to it.
(Instead of making every possible excuse not to work with that API and instead doing something else where they can make some progress without going insane.)
Worst is redo it all
They probably got stuff done, just not the things you left half implemented code for...
Just started a new job last week. Ive been in the industry for 3 years so not completely junior but getting in to a new codebase is always rough. Especially when only 1 huge library file is documented, every component is cluttered af and most variables and parameter names are 1 character long.
Doesnt help that functions are 100 lines either when each the parameter names makes the logic incomprehensible.