this post was submitted on 15 Oct 2024
181 points (99.5% liked)

Programming

17186 readers
467 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 !webdev@programming.dev



founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] 0x0@programming.dev 109 points 12 hours ago (7 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...

[–] sorval_the_eeter@lemmy.world 3 points 1 hour ago* (last edited 1 hour ago) (1 children)

I keep seeing a pattern of sre/devops/sysadmin tasks being given back to developers and canning the SREs. Hard to understand why. Then some of the SWE get stuck basically focussing on infra SRE stuff and become unwilling SRE more or less. Circle of life? Do the old devops folks get made into glue or something?

[–] 0x0@programming.dev 2 points 1 hour ago

Do the old devops folks get made into glue or something?

If i interpreted the "trend" correctly, "devops" was bastardized away from its original meaning to now mean "sysadmin", at least in most cases.

[–] delirium@lemmy.world 3 points 1 hour ago

My boss legit says that he will give me some time to work on it every 2-3 months and then drops a “customer requires X feature and I promised that we will deliver in one week”. And mind you we have to patch up to 3 major versions in the past to back port the new feature because client haven’t upgraded and won’t in near future… which means sometimes our major releases are 60-70% same as our minor patches for old versions. Semvering much?

[–] FizzyOrange@programming.dev 4 points 3 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.

[–] 0x0@programming.dev 2 points 1 hour ago

Use overestimation padding, eh?

[–] IllNess@infosec.pub 5 points 3 hours ago

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

[–] Cold_Brew_Enema@lemmy.world 8 points 7 hours ago

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

[–] Croquette@sh.itjust.works 17 points 10 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".

[–] zqwzzle@lemmy.ca 28 points 12 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.

[–] Tanoh@lemmy.world 9 points 5 hours ago (1 children)

But then it is the developers fault, never management

[–] sorval_the_eeter@lemmy.world 2 points 1 hour ago

Seen a lot of that too. Execs who thinks all the devs are idiots and would be lost without their genius guidance, phoned in from a luxury remote location while all of us have to return to the office full time. Then stuff fails and we "pivot" to the next badly thought out fiasco. I guess it pays the bills.

[–] ogmios@sh.itjust.works 30 points 12 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!