this post was submitted on 02 Mar 2025
752 points (99.3% liked)

People Twitter

5974 readers
2198 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
[email protected]
[email protected]
752
Good luck, everybody (lemmy.world)
submitted 1 day ago by The_Picard_Maneuver to c/[email protected]
21 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 18 points 12 hours 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 3 points 10 hours 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.

[–] [email protected] 2 points 9 hours 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