this post was submitted on 02 Mar 2025
801 points (99.4% liked)

People Twitter

7542 readers
1274 users here now

People tweeting stuff. We allow tweets from anyone.

RULES:

  1. Mark NSFW content.
  2. No doxxing people.
  3. Must be a pic of the tweet or similar. No direct links to the tweet.
  4. No bullying or international politcs
  5. Be excellent to each other.
  6. Provide an archived link to the tweet (or similar) being shown if it's a major figure or a politician.

founded 2 years ago
MODERATORS
 
top 16 comments
sorted by: hot top controversial new old
[–] unexposedhazard@discuss.tchncs.de 98 points 4 months ago

I mean, i asked them to allocate time for me to write documentation and they didnt reply to those emails. Its not unmaintainable, but its still not very well documented apart from some comments on the more complex or intransparent sections of the code.

[–] Randelung@lemmy.world 73 points 4 months ago (1 children)

I was on the receiving end, except the roles are reversed. Dude retired and left an undocumented spaghetti mess.

But! He worked on a code base by himself for two years, on a subject matter he knew nothing about, in a language he didn't know, and kept asking management for help. I don't blame him a single bit, not the tiniest iota. 200% management fault, once for having him do that and once again for ignoring his cries for help.

[–] loics2@lemm.ee 12 points 4 months ago

It feels like you're describing one of my previous jobs

[–] Kolanaki@pawb.social 68 points 4 months ago* (last edited 4 months ago) (2 children)

If {Kolanaki != Employed_Here} then {exit()};

Making myself unfirable. 😎

[–] sundrei@lemmy.sdf.org 105 points 4 months ago (1 children)
[–] A_Union_of_Kobolds@lemmy.world 37 points 4 months ago (1 children)

Goddamn that's a great quote

[–] Viking_Hippie@lemmy.dbzer0.com 34 points 4 months ago

I wish I'd known about it in 2020 when the powers that be made it excruciatingly clear that "essential worker" was code for "acceptable sacrifice"..

[–] jaybone@lemmy.world 4 points 4 months ago (1 children)

And making your coworkers hate you.

[–] Kolanaki@pawb.social 19 points 4 months ago

There is only a problem if I am not their co-worker, tho. 🤷🏻‍♂️

[–] GluWu@lemm.ee 68 points 4 months ago

Oh, were you going to give me a raise that's more than inflation? No? More than 6 days off a year? Oh, no? Match a 401k? ...no. Yeah, good luck with the clusterfuck. The little energy I had beyond just making this function went into purposely obfuscating everything. Just give it to your AI, that'll sort it out.

[–] Septimaeus 25 points 4 months ago (1 children)

FYI: it’s typically management who cuts corners, whether in hiring or process. I’ve met a few exceptions but most devs take pride in their work.

Tips:

  1. if you’re experienced and management insists on cluegy solutions, either refuse or leave a trail of tickets and comments re: technical debt for the next dev.
  2. If you’re not experienced, or if you feel out of your depth and have no senior to turn to, know that you will with time and just try do your best.
  3. In either case, experienced devs will understand the situation and won’t judge you.
  4. Also in either case, fire the client.
[–] asdfasdfasdf@lemmy.world 5 points 4 months ago (1 children)

Another method I've used extensively is to block code reviews on unmaintainability. Management has insight into high level stuff, but devs where I work dictate what gets merged.

[–] Croquette@sh.itjust.works 3 points 4 months ago

Whenever I can, my code isn't ready yet, it needs a few tweaks until the code is viable. That way, if I can never touch the code again, it has a chance to not be terrible in the future

[–] HootinNHollerin@lemmy.dbzer0.com 18 points 4 months ago

Taking a job at DOGE

[–] some_guy@lemmy.sdf.org 13 points 4 months ago

This was my first laugh of the day. Cheers.

[–] NigelFrobisher@aussie.zone 3 points 4 months ago

This explains a lot.