@state_electrician@discuss.tchncs.de
Post #324988
2026-02-17 20:04 UTC
Replies (17)
-
@First_Thunder@lemmy.zip 2026-02-17 20:07
Thank god we are going opposite to the Tim direction
-
@Gyroplast@pawb.social 2026-02-17 20:19
The 15yo "source" for the sloppy plagiarism: https://nvie.com/posts/a-successful-git-branching-model/
-
@balsoft@lemmy.ml 2026-02-18 00:12
I really hope "morging continvoucly" becomes a meme and is used to mock microsoft forever
-
@Ephera@lemmy.ml 2026-02-18 05:26
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?
-
@princess@lemmy.blahaj.zone 2026-02-17 21:02
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
-
@anhkagi@jlai.lu 2026-02-18 09:14
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.
-
@goatinspace@feddit.org 2026-02-17 21:13
-
@pivot_root@lemmy.world 2026-02-17 23:34
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.
-
@jcorvera@quokk.au 2026-02-17 21:31
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.
-
@Grail@multiverse.soulism.net 2026-02-18 16:21
Remember when morgius morged all over those guys?
-
@Slashme@lemmy.world 2026-02-19 12:22
git log --pretty=fucked-up
-
@RustyNova@lemmy.world 2026-02-17 22:42
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 2026-02-17 22:43
Tim is going backwards in time
-
@victorz@lemmy.world 2026-02-18 01:25
> Stat of release The image genAI is also from Boston.
-
@0ops@piefed.zip 2026-02-17 21:53
Major featue UwU
-
@Gonzako@lemmy.world 2026-02-18 07:41
I just made master become what gets pushed to the actual website so I do have to take it into consideration
-
@rtxn@lemmy.world 2026-02-17 22:16