this post was submitted on 15 Oct 2024
174 points (99.4% liked)

Programming

17186 readers
503 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]



founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 101 points 11 hours ago (5 children)

Technical debt is the number one cause of developer frustration. Working with imperfect systems demoralizes programmers, making it difficult to do quality work.

I'd wager not being given time to tackle technical debt is indeed frustating...

[–] [email protected] 4 points 2 hours ago (2 children)

The secret is just to do it anyway. I have yet to work in a job where anyone actively stopped me fixing technical debt, even if they never asked me to do it.

[–] [email protected] 1 points 2 minutes ago

Use overestimation padding, eh?

[–] [email protected] 3 points 2 hours ago

Depends on the work load. The company should make time for that and you should get paid for it.

[–] [email protected] 7 points 5 hours ago

It is. Source: We've had the same issues for years, but never get any time allotted to fix them.

[–] [email protected] 16 points 9 hours ago

Yeah, that's probably more the issue. We've seen too many times throwaway code become production code because "it works already, we need to move forward".

[–] [email protected] 30 points 10 hours ago

I don't care what your fancy RAMrod doohickeys say Johnson! We need that system up tomorrow so we can reach our quarterly earning projections for the shareholder's meeting!

[–] [email protected] 27 points 10 hours ago (1 children)

It’s hilarious when the identified problems come back around to bite the organization, when the priorities have been to work on poorly specc’d features instead.

[–] [email protected] 5 points 3 hours ago

But then it is the developers fault, never management