Programming

26138 readers

876 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

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

UlrikHD@programming.dev

bugsmith@programming.dev

Spyro@programming.dev

Good, Fast, Cheap: Pick 3 or Get None (loup-vaillant.fr)

submitted 2 months ago by HaraldvonBlauzahn@feddit.org to c/programming@programming.dev

8 comments fedilink hide all child comments

Matches my own experience when working on software where quality matters, like large and long-running scientific projects: Even if there are tight time constraints, you won't sacrifice quality, because that would make you slower.

you are viewing a single comment's thread
view the rest of the comments

[–] HaraldvonBlauzahn@feddit.org 5 points 2 months ago* (last edited 2 months ago)

In my experience that attitude bites in under 6 months. I'm already wasting entire days sorting out messes that they neglected to deal with.

That's pretty much in line with what John Ousterhout writes. I think if you deal with multi-threading / locking / diszributed systems stuff, that time span is likely to be lower.