this post was submitted on 25 Mar 2024
54 points (95.0% liked)

Programming

17408 readers
89 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
[–] MonkderZweite@feddit.ch 0 points 7 months ago* (last edited 7 months ago) (1 children)

In my humble opinion, you shouldn't be allowed to participate in big projects if you don't fulfill some minimal requirements.

Reminds me of the crack i had to explain the concept of technical debt. He was the main maintainer of a years old Xamarin project, he took over from his precursor.

[–] magic_lobster_party@kbin.run 6 points 7 months ago* (last edited 7 months ago) (1 children)

Most software is built under non-ideal circumstances. Especially in the beginning there’s often tight deadlines involved.

“Good news! We finally got a new customer! Looks like we will survive this month! Bad news. We sold a feature we don’t have yet and oh, we also promised to have it delivered by tomorrow morning, so hurry up!”

[–] lysdexic@programming.dev 4 points 7 months ago

Most software is built under non-ideal circumstances. Especially in the beginning there’s often tight deadlines involved.

Exactly this.

I think a bunch of people commenting in this thread on the virtues of rewriting things from scratch using the flavour of the month are instead showing the world they have zero professional experience working on commercial software projects. They are clearly oblivious to very basic and pervasive constraints that anyone working on software for a living is very well aware.

Things like prioritizing how a button is laid out over fixing a rarely occurring race condition is the norm in professional settings. You are paid to deliver value to your employer, and small things like paying technical debt are very hard sells for project managers running tight schedules.

Yet, here we are, seeing people advocating complete rewrites and adding piles of complexity while throwing out major features, and doing so with a straight face.

Unbelievable.