• 0 Posts
  • 25 Comments
Joined 3 years ago
cake
Cake day: July 25th, 2023

help-circle











  • Really bigger updates obviously require a major version bump to signify to users that there is potential stability or breakage issues expected.

    If your software is following semver, not necessarily. It only requires a major version bump if a change is breaking backwards compatibility. You can have very big minor releases and tiny major releases.

    there was more time for people to run pre-release versions if they are adventurous and thus there is better testing

    Again, by experience, this is assuming a lot.


  • From experience shipping releases, “bigger updates” and “more tested” are more or less antithetical. The testing surface area tends to grow exponentially with the amount of features you ship with a given release, to the point I tend to see small, regular releases, as a better sign of stability.



  • Considering how little we actually know, how much we are still figuring out today, how wrong we once were, and most definitely still are on many things, about said nature, the naturalistic argument is IMHO rather weak. The argument silently assumes too many things, at least with our current knowledge - that human beings do actually have an inherent nature, that said nature is uniform enough across the whole species to make that generalization, that said nature is inevitable and can’t be evolved past or rationalized against, that it always was the case and will always be, etc.




  • I’m not sure if you’re agreeing or trying to disprove my previous comment - IMHO, we are saying the exact same thing. As long as those stranded travelers or data breaches cost less than the missed business from not getting the product out in the first place, from a purely financial point of view, it makes no sense to withhold the product’s release.

    Let’s be real here, most developers are not working on airport ticketing systems or handling millions of users’ private data, and the cost of those systems failing isn’t nearly as dramatic. Those rigid procedures civil engineers have to follow come from somewhere, and it’s usually not from any individual engineer’s good will, but from regulations and procedures written from the blood of previous failures. If companies really had to feel the cost of data breaches, I’d be willing to wager we’d suddenly see a lot more traction over good development practices.