this post was submitted on 01 Sep 2023
254 points (96.4% liked)

Programming

17495 readers
149 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
[–] __little_omega@lemmy.world 16 points 1 year ago (3 children)

If programmers stick to what they know and not try to solve every problem at hand with the latest thing/programming language they've learned then there would be fewer bugs and projects would end by the estimated dates.

[–] nephs@lemmygrad.ml 2 points 1 year ago (1 children)

I think failed estimated dates just highlight how much we don't know about ourselves, our systems and our own knowledge.

It is the abyss of the unknown talking back to us. We have the privilege of having the stuff we don't know thrown back at us to prove us wrong. And we often fail to be humbled by it.

[–] dudinax@programming.dev 3 points 1 year ago

Much of the job is dealing with the unknown. A surprise in scheduling can either shorten a task or lengthen it. It can't be shortened past the time it takes to recognize it's finished, but it can be lengthened indefinitely.