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.
I’m a Ruby developer but recently needed to solve a problem from within a non-Ruby Kubernetes container.
If I stuck with what I know I would’ve had to include the entire Ruby runtime into a totally unrelated application’s image.
Knowing exactly how to solve the problem in Ruby but not wanting to add hundreds of Ruby scripts everywhere, I found Crystal was the perfect fit for my needs.
I was able to write a slim sidecar container. The Dockerfile compiles it into a static binary, trashes the entire toolchain (FROM build) and the resulting image is just a few megabytes.
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.
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.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programming@programming.dev
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
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.
…but it can be nice to dabble.
I’m a Ruby developer but recently needed to solve a problem from within a non-Ruby Kubernetes container.
If I stuck with what I know I would’ve had to include the entire Ruby runtime into a totally unrelated application’s image.
Knowing exactly how to solve the problem in Ruby but not wanting to add hundreds of Ruby scripts everywhere, I found Crystal was the perfect fit for my needs.
I was able to write a slim sidecar container. The Dockerfile compiles it into a static binary, trashes the entire toolchain (
FROM build) and the resulting image is just a few megabytes.deleted by creator
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.
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.