this post was submitted on 20 Nov 2025
17 points (90.5% liked)

Programming

23517 readers
266 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 2 years ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
MaungaHikoi@lemmy.nz
UlrikHD@programming.dev
17
Why Does Development Slow? (tidyfirst.substack.com)
submitted 6 hours ago by codeinabox@programming.dev to c/programming@programming.dev
9 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] falseWhite@lemmy.world 20 points 5 hours ago* (last edited 5 hours ago) (1 children)

So basically refactor old features and code to remove tech debt before starting work on new features, so it's easier to implement them.

Developers always knew that. PMs always hated that.

[–] calliope@retrolemmy.com 9 points 4 hours ago

Refactoring is great, but there’s more.

The larger a project is or the busier developers are, the harder it is to become acclimated to parts of the code, too.

There are a few more examples from the article:

Bugs pile up. The build slows. Backwards compatibility imposes its own tax on progress. Original team members move on, while new members take time to acclimate.

He doesn’t mention this, but it also takes time to re-acclimate yourself to things you wrote six months ago. Good code and tests help but developers are human beings.