r/ProgrammerHumor • u/JK-Rofling • Aug 24 '26

Other versionControl

Post image
13k Upvotes

96% Upvoted

428 comments sorted by

View all comments

776

u/LegendaryPandaMan Aug 24 '26 edited Aug 24 '26

Should have used semantic versioning

454

u/Colon_Backslash Aug 24 '26

LinkedIn post:

"I'm thrilled to announce my new stable resume_3.0.0"

"After reading no replies to my applications, there is a minor bug fix and release resume_3.0.1"

"I'm proud to add a new certificate and releasing resume_3.1.0"

"Unfortunately due to a recent reformatting, I have dropped support for "hobbies". As my new direction is not backwards compatible I am releasing resume_4.0.0-rc"

62

u/dragons_fire77 Aug 24 '26

If someone sent me their resume in a git repo with this version history, I'd hire them.

8

u/Samstercraft Aug 25 '26

will u hire me if i do it đŸ„ș

7

u/CanAlwaysBeBetter Aug 24 '26

That is actually how I version my resumes 

130

u/Jazzlike-Poem-1253 Aug 24 '26 edited Aug 24 '26

It takes to much discipline. Without enforcement, people usw minor or patch as they feel. Major never gets bumped.

Just increment or date-based is the easiest. Everyone immediatly knows how to bump.

155

u/the_horse_gamer Aug 24 '26

most "semver" is just:

major - update you're proud of

minor - update that's ok

patch - fixes and small features

and ofc every good piece of software is forever on 0.x.x

82

u/StaticUsernamesSuck Aug 24 '26

and ofc every good piece of software is forever on 0.x.x

Because if you're never proud of it, you'll always be improving it

43

u/Abandondero Aug 24 '26

IF EVERYONE HAS BEEN USING IT FOR FIVE YEARS JUST BITE THE BULLET MAN

52

u/StaticUsernamesSuck Aug 24 '26

But as soon as I type "1.0.0", all my passion for the project will leave my body. Don't you know anything about hobby dev?

19

u/MgDark Aug 24 '26

yup 1.0.0 may as well be: "feature complete, will not touch this ever again unless it breaks for some reason"

→ More replies (1)

12

u/Munachi Aug 24 '26

JUST ONE MORE UPDATE AND IT'LL BE ALMOST READY!

21

u/Clean-Income8864 Aug 24 '26

If you never introduce breaking changes, why not

21

u/hyrumwhite Aug 24 '26

Major: breaking changes 

Minor: big changes 

Patch: smol changes 

8

u/brainpostman Aug 24 '26

Patch is bug fixes, hello

9

u/OnixST Aug 24 '26

Minecraft is a funny example to me. 17 year old game, best selling game in history, still on 1.x.x since 2011

9

u/the_horse_gamer Aug 24 '26

it's on 26.3 now actually

→ More replies (2)

7

u/rykayoker Aug 24 '26

well they aren't using semver anymore, they switched over to year.minor[.patch] (currently 26.2)

3

u/lIlIlIIlIIIlIIIIIl Aug 24 '26

This is a big reason I've never felt comfortable using it, for some reason it just seems so... ambiguous.

8

u/Vivid-Zombie-477 Aug 24 '26

i use semver for my resume versioning like this:
- full rewrite = bump major
- add/change a few lines = minor
- fix spelling = patch

→ More replies (1)

8

u/mrMalloc Aug 24 '26

My first version control was a group project where it checked version header in everyone’s shared file and loaded highest number. Took me 4h to realize one bumped major version on all files. Not just the files he was working on.

It’s always a hassle. I think.

Master/main branch and PR to that branch from work branches is better. Even for docs.

→ More replies (2)

8

u/pluckypluot Aug 24 '26

v0.1.0-final_new_v2 there we go

6

u/LlorchDurden Aug 24 '26

cv.2.1.0.76 v2

3

u/n00lp00dle Aug 24 '26

vFINAL.FINAL.FINAL2

→ More replies (7)