that’s with the assumption that the smallest increment was used every time
I sometimes increment things by adding the next decimal place
note: I am not a developer, just a dude making tools at work. but I somehow always end up incrementing something now and then from 1.21 to 1.211 because I wanted to avoid the “1.21 new actually newest” situation and bumping to 1.22 didn’t make sense. it’s like temporary versioning for me, WIP files
Well that explains why I’m on version
0.0.7899999999998765
deleted by creator
Most of the mistakes they have to fix are incorrect version numbering.
AI slop bbyyyyyyy!!!
Weak humans would use 250 million years, strong AI can slop it in 1 year.
/S
I have seen people just add '9’s to it, so to not upgrade the minor, so 2.6.997 gets 2.6.9997 and so on
Some people cannot math.
Wow a little bit of math is a dangerous thing
!theydidthemath@mander.xyz
And here I was holding my breath for the legendary 0.0.7899999999998766. Thanks for ruining all my dreams.
that’s with the assumption that the smallest increment was used every time
I sometimes increment things by adding the next decimal place
note: I am not a developer, just a dude making tools at work. but I somehow always end up incrementing something now and then from 1.21 to 1.211 because I wanted to avoid the “1.21 new actually newest” situation and bumping to 1.22 didn’t make sense. it’s like temporary versioning for me, WIP files
deleted by creator
so I actually use various different systems depending on my mood that day.
maybe I add a dash, maybe I use another decimal, maybe I use alpha characters.
none of it matters because they’re wiped out a few hours later
Sub version tags make sense but for the the love of pie if you’re going to use a number at least separate it from the others, like
1.21-1no it’s more like
Copy of New File (2)_finalThey go up to version 0.0.8, 0.0.9, then they go to 0.0.91, 0.0.92, … 0.0.99, 0.0.991, …
You need to cast that float.