Morge continvoucly

6 months ago by state_electrician to c/programmer_humor

This was from official Microslop documentation https://web.archive.org/...

load all comments

Gyroplast 80 points 6 months ago

The 15yo "source" for the sloppy plagiarism: https://nvie.com/...

save

path: 0 22196151, hotness: undefined, score: 80, children: 9

credo 37 points 6 months ago

OP responded to the great Morge: https://nvie.com/posts/15-years-later/

save

path: 0 22196151 22202536, hotness: undefined, score: 37, children: 0

Skullgrid 24 points 6 months ago

holy fuck, it's basically the time I followed a tutorial for generating "a witch" for AI art, and ended up with a horribly mangled MTG card

save

path: 0 22196151 22196513, hotness: undefined, score: 24, children: 0

Ephera 12 points 6 months ago

Wow, it stole it badly enough that it might not count as copyright infringement in court, but it also stole it badly enough that it isn't useful at all.

save

path: 0 22196151 22202567, hotness: undefined, score: 12, children: 0

pizza_the_hutt 10 points 6 months ago

It's still not a bad system if you have to support and provide bugfixes for multiple versions of software. However, if you only support the latest version and only create bug fixes and features based on the latest release or main branch, then git-flow is way overkill.

save

path: 0 22196151 22196320, hotness: undefined, score: 10, children: 5

lmmarsano 13 points 6 months ago

It's an atrocious, pointlessly complicated system resulting in convoluted project histories prone to confusion. Trunk-based development with sensible tags of releases & hotfixes achieves the same thing without the junk complexity. Git flow isn't overkill, it's just ill-conceived.

save

path: 0 22196151 22196320 22197322, hotness: undefined, score: 13, children: 4

Rules

Rules