346
Morge continvoucly (discuss.tchncs.de)
top 50 comments
sorted by: hot top controversial new old
[-] First_Thunder@lemmy.zip 97 points 2 months ago

Thank god we are going opposite to the Tim direction

[-] lonesomeCat@lemmy.ml 8 points 2 months ago

Yeah, Fuck Tim

[-] Gyroplast@pawb.social 81 points 2 months ago
[-] credo@lemmy.world 37 points 2 months ago
[-] apotheotic@beehaw.org 25 points 2 months ago
[-] Avicenna@programming.dev 3 points 2 months ago* (last edited 2 months ago)

You gotto love how the AI took the axis on the left, was confused enough from its tail that it thought it must be pointing in the opposite direction to development flow and then went "welp if it is going in the other direction, the label "time" must be a typo. Ima make it Tim the time traveller instead". Ofcourse none of it happened like this, but I would like to imagine that it did.

[-] Skullgrid@lemmy.world 24 points 2 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

[-] Ephera@lemmy.ml 12 points 2 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.

[-] pizza_the_hutt@sh.itjust.works 10 points 2 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.

[-] lmmarsano@group.lt 14 points 2 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.

[-] thesmokingman@programming.dev 4 points 2 months ago

This is a joke, right? OneFlow isn’t trunk-based development and is actually gitflow with different steps. I have yet to see any org actually use trunk-based development mostly because I’ve not seen cherry-picking from the trunk adopted at any large scale.

[-] chunkystyles@sopuli.xyz 5 points 2 months ago

I pushed my team to use trunk based development. We did cherry-picks from trunk to release branches for a couple years with no issues. Since then, I've written a GitHub action that automates the cherry-picks based on tickets in the commit messages.

But even before the automation, it drastically improved our dev processes.

We weren't on Git Flow exactly, but it was a bastardized version of it.

Having used TBD successfully for like 5-6 years now. I can't imagine using Git Flow.

load more comments (1 replies)
[-] draycs@lemmy.world 3 points 2 months ago

What is large scale to you? We have 100-200 developers doing something fairly close to trunk based development. Including cherry picking from trunk when possible (not always practical for sufficiently old release branches)

[-] balsoft@lemmy.ml 59 points 2 months ago

I really hope "morging continvoucly" becomes a meme and is used to mock microsoft forever

[-] criss_cross@lemmy.world 23 points 2 months ago

I for one will use it continvoucly.

[-] Ephera@lemmy.ml 53 points 2 months ago

To be honest, what I'm most mad about isn't the typoes, it's that someone generated this image and figured, yeah alright, that will clear things up.

On some level you want to believe that even if someone does not come up with a proper concept for a visualization, that they still check what the AI shat out, so that it's at the very least not conceptually wrong and not confusing.

This image isn't just shitty, it's actively worse than having no visualization. They could've generated that, chuckled, and not used it. Just how do you blunder your perception check so badly that you decide to include it anyways?

[-] Gyroplast@pawb.social 31 points 2 months ago

There is the decades-old adage:

Incorrect documentation is worse than no documentation.

That's why I never comment my code. The documentation is in the .h files. The "h" means "help".

[-] Railcar8095@lemmy.world 17 points 2 months ago

In my company the h means "haha, what were you expecting?"

[-] mcv@lemmy.zip 12 points 2 months ago

That is exactly the problem. I understand people using AI to make things. I don't understand blindly publishing AI slop without verifying it's correct.

Everybody using genAI has to understand that AI will often be wrong, and frequently ridiculous, and that it's up to you to ensure that what you deliver is correct.

And because nobody likes to review other people's work (most people are terrible and sloppy reviewers), it's better to put yourself in the center: have AI propose ideas or review the result, but you make the thing. That's how you ensure everything passes through your hands.

[-] ZomieChicken@sh.itjust.works 6 points 2 months ago

In a proper PnPRPG/Tabletop RPG game, a truly spectacular blunder feels like a success to the person who failed. Walk into a bar and critfail both your Communications check, and the "Oh crap, I failed that badly. Can I save this by doing ______?" follow-up Communications check? You think you did fine, but now the entire bar thinks you are a truly crazy person, and treat you with respect only because they think you're going to shiv them in the neck if they get out of line.

[-] Avicenna@programming.dev 4 points 2 months ago

That is likely because depending on AI makes you gradually less and less likely to cross-check and verify stuff. For some the whole appeal is the belief that they can get the answer/product they want in a second, ready to go out of the box and without having to spend any mental energy.

[-] princess@lemmy.blahaj.zone 47 points 2 months ago* (last edited 2 months ago)

git Morge perfec t flow for put code in to re\lease! inside very Bronch and Featue code morge continvoucly put code in Git Morge. no problems ever in gitt morge because good Flow and Barnch for code morge conflict of big code releas. Agit Morge yes a place for a code put code in git morge can trust Tirm for giveing good morge to code. friend morge

[-] xep@discuss.online 12 points 2 months ago

Wish I hadn't read this while drinking my tea.

[-] JetpackJackson@feddit.org 6 points 2 months ago

I know this is a meme but what is it from

[-] princess@lemmy.blahaj.zone 21 points 2 months ago
[-] JetpackJackson@feddit.org 6 points 2 months ago
[-] princess@lemmy.blahaj.zone 12 points 2 months ago

No worries! pelcan Mouth perfec t meme for make snowclone of.

[-] goatinspace@feddit.org 3 points 2 months ago

From 1985 when plutonium was pure and future considered 2015.

[-] anhkagi@jlai.lu 36 points 2 months ago

Even without considering the typos, the diagram is incomprehensible with all these arrows pointing in every direction and textboxes placed randomly. I had to look at the original to understand it.

[-] pivot_root@lemmy.world 30 points 2 months ago

Well, that explains a lot about the product quality. Their entire development workflow is a complete fucking mess.

  • Long-lived feature branches.
  • Creating merge commits to main just for the sole purpose of tagging them as releases while also maintaining separate release branches.
  • Force-pushing tags to incorporate post-release hotfixes instead of releasing minor patch updates.
  • Taking bugfixes from releases and merging them back into the development branch (have they not heard of cherry-pick?)
  • Always using merges even when a rebase would be easier to follow and keep the history more straightforward.
[-] figjam@midwest.social 33 points 2 months ago

Whats a merge? We be morging up here

[-] A7thStone@lemmy.world 25 points 2 months ago

It's morgin time

[-] Ephera@lemmy.ml 25 points 2 months ago

I admire your ability to interpret anything into this fucking picture...

[-] goatinspace@feddit.org 29 points 2 months ago
[-] filcuk@lemmy.zip 7 points 2 months ago

I feel it's a bad sign that I'm saving this meme for use at work

[-] princess@lemmy.blahaj.zone 11 points 2 months ago

Everybody has a testing environment. Some people are lucky enough enough to have a totally separate environment to run production in.

[-] jcorvera@quokk.au 13 points 2 months ago

And Microsoft stole it from a different developer, who posted it back in 2011... and then ran it through Copilot without even checking it thoroughly before adding it to training documentation.

[-] StellarSt0rm@lemmy.world 4 points 2 months ago* (last edited 2 months ago)

Makes me wonder how much of the training documentation is AI generated...

[-] jcorvera@quokk.au 4 points 2 months ago

Considering their recent output?

Probably all the latest pubs.

[-] Grail@multiverse.soulism.net 12 points 2 months ago

Remember when morgius morged all over those guys?

[-] Slashme@lemmy.world 10 points 2 months ago
git log --pretty=fucked-up
[-] RustyNova@lemmy.world 7 points 2 months ago

I love git flow but the GitHub tooling is bad. It forces you into GitHubflow which is very confusing for those building from source

[-] Avicenna@programming.dev 6 points 2 months ago

Tim is going backwards in time

[-] egrets@lemmy.world 6 points 2 months ago
[-] Avicenna@programming.dev 5 points 2 months ago

Tiꦟ doesn't just morge continvoucly, he goes back in time and fixes his mistakes before they ever happen.

[-] victorz@lemmy.world 4 points 2 months ago

Stat of release

The image genAI is also from Boston.

[-] 0ops@piefed.zip 3 points 2 months ago

Major featue UwU

[-] Gonzako@lemmy.world 2 points 2 months ago

I just made master become what gets pushed to the actual website so I do have to take it into consideration

load more comments
view more: next ›
this post was submitted on 17 Feb 2026
346 points (98.3% liked)

Programmer Humor

31092 readers
271 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS