Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Cyborg)
  • No Skin
Collapse
Brand Logo

CIRCLE WITH A DOT

  1. Home
  2. Uncategorized
  3. This is truly glorious #AISlop from #Microslop in their "Introduction to Github" course.

This is truly glorious #AISlop from #Microslop in their "Introduction to Github" course.

Scheduled Pinned Locked Moved Uncategorized
aislopmicroslop
142 Posts 91 Posters 2 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • dazfuller@mstdn.socialD dazfuller@mstdn.social

    This is truly glorious #AISlop from #Microslop in their "Introduction to Github" course.

    I don't know why Tim is working in the opposite direction, but I can see that he never once "morges" his code back into develop, let alone doing it "continvoucly"

    Link Preview Image
    Components of the GitHub flow - Training

    Learn to use the components of the GitHub flow

    favicon

    (learn.microsoft.com)

    jdstewart2008@mastodon.socialJ This user is from outside of this forum
    jdstewart2008@mastodon.socialJ This user is from outside of this forum
    jdstewart2008@mastodon.social
    wrote last edited by
    #6

    @dazfuller 3rd largest publicly-traded company in the U.S.

    1 Reply Last reply
    0
    • dazfuller@mstdn.socialD dazfuller@mstdn.social

      This is truly glorious #AISlop from #Microslop in their "Introduction to Github" course.

      I don't know why Tim is working in the opposite direction, but I can see that he never once "morges" his code back into develop, let alone doing it "continvoucly"

      Link Preview Image
      Components of the GitHub flow - Training

      Learn to use the components of the GitHub flow

      favicon

      (learn.microsoft.com)

      ohmrun@indieweb.socialO This user is from outside of this forum
      ohmrun@indieweb.socialO This user is from outside of this forum
      ohmrun@indieweb.social
      wrote last edited by
      #7

      @dazfuller That's Tim travelling back in time to fix his morge strategy.

      loosenut@genart.socialL bartholin@fops.cloudB leo_wallentin@mastodon.socialL jennyfluff@chitter.xyzJ 4 Replies Last reply
      0
      • dazfuller@mstdn.socialD dazfuller@mstdn.social

        This is truly glorious #AISlop from #Microslop in their "Introduction to Github" course.

        I don't know why Tim is working in the opposite direction, but I can see that he never once "morges" his code back into develop, let alone doing it "continvoucly"

        Link Preview Image
        Components of the GitHub flow - Training

        Learn to use the components of the GitHub flow

        favicon

        (learn.microsoft.com)

        rhempel@mstdn.caR This user is from outside of this forum
        rhempel@mstdn.caR This user is from outside of this forum
        rhempel@mstdn.ca
        wrote last edited by
        #8

        @dazfuller This is just GitFlow reinterpreted by AI and it's honestly pretty much why developers sometimes hate git 🙂

        Move to Trunk Based Development (with a coach if you need it) and look back on this model and laugh like a maniac.

        dazfuller@mstdn.socialD 1 Reply Last reply
        0
        • ohmrun@indieweb.socialO ohmrun@indieweb.social

          @dazfuller That's Tim travelling back in time to fix his morge strategy.

          loosenut@genart.socialL This user is from outside of this forum
          loosenut@genart.socialL This user is from outside of this forum
          loosenut@genart.social
          wrote last edited by
          #9

          @ohmrun @dazfuller

          That was the beginning of the great Tim wars, which continue to this day

          ohmrun@indieweb.socialO thuri@metalhead.clubT 2 Replies Last reply
          0
          • rhempel@mstdn.caR rhempel@mstdn.ca

            @dazfuller This is just GitFlow reinterpreted by AI and it's honestly pretty much why developers sometimes hate git 🙂

            Move to Trunk Based Development (with a coach if you need it) and look back on this model and laugh like a maniac.

            dazfuller@mstdn.socialD This user is from outside of this forum
            dazfuller@mstdn.socialD This user is from outside of this forum
            dazfuller@mstdn.social
            wrote last edited by
            #10

            @rhempel I mean, it _should_ be gitflow, and yet the AI somehow made it more complicated and incorporated temporal dynamics

            rhempel@mstdn.caR jsamcfarlane@mastodon.ieJ 2 Replies Last reply
            0
            • ohmrun@indieweb.socialO ohmrun@indieweb.social

              @dazfuller That's Tim travelling back in time to fix his morge strategy.

              bartholin@fops.cloudB This user is from outside of this forum
              bartholin@fops.cloudB This user is from outside of this forum
              bartholin@fops.cloud
              wrote last edited by
              #11
              @ohmrun @dazfuller It's Tiണ, or maybe Tiሰሰሰ
              moira@mastodon.murkworks.netM 1 Reply Last reply
              0
              • loosenut@genart.socialL loosenut@genart.social

                @ohmrun @dazfuller

                That was the beginning of the great Tim wars, which continue to this day

                ohmrun@indieweb.socialO This user is from outside of this forum
                ohmrun@indieweb.socialO This user is from outside of this forum
                ohmrun@indieweb.social
                wrote last edited by
                #12

                @loosenut behold the enborkening.

                1 Reply Last reply
                0
                • R relay@relay.mycrowd.ca shared this topic
                  R relay@relay.infosec.exchange shared this topic
                • dazfuller@mstdn.socialD dazfuller@mstdn.social

                  @rhempel I mean, it _should_ be gitflow, and yet the AI somehow made it more complicated and incorporated temporal dynamics

                  rhempel@mstdn.caR This user is from outside of this forum
                  rhempel@mstdn.caR This user is from outside of this forum
                  rhempel@mstdn.ca
                  wrote last edited by
                  #13

                  @dazfuller It should have just been a link to the (awful) Gitflow image everyone uses.

                  Instead it's a clear demonstration of Microsoft eating its own AI dogfood, and finding out that it's rotten, and they don't have the common sense to sniff it before eating it.

                  They have really lost the thread ...

                  dazfuller@mstdn.socialD 1 Reply Last reply
                  2
                  0
                  • dazfuller@mstdn.socialD dazfuller@mstdn.social

                    This is truly glorious #AISlop from #Microslop in their "Introduction to Github" course.

                    I don't know why Tim is working in the opposite direction, but I can see that he never once "morges" his code back into develop, let alone doing it "continvoucly"

                    Link Preview Image
                    Components of the GitHub flow - Training

                    Learn to use the components of the GitHub flow

                    favicon

                    (learn.microsoft.com)

                    alxndr@tech.lgbtA This user is from outside of this forum
                    alxndr@tech.lgbtA This user is from outside of this forum
                    alxndr@tech.lgbt
                    wrote last edited by
                    #14

                    @dazfuller Only bugfixes!

                    1 Reply Last reply
                    0
                    • rhempel@mstdn.caR rhempel@mstdn.ca

                      @dazfuller It should have just been a link to the (awful) Gitflow image everyone uses.

                      Instead it's a clear demonstration of Microsoft eating its own AI dogfood, and finding out that it's rotten, and they don't have the common sense to sniff it before eating it.

                      They have really lost the thread ...

                      dazfuller@mstdn.socialD This user is from outside of this forum
                      dazfuller@mstdn.socialD This user is from outside of this forum
                      dazfuller@mstdn.social
                      wrote last edited by
                      #15

                      @rhempel I tried to do the nice thing and filed an issue against it. Not holding my breath though, the last time I did that it was hanging around for 2 years until they deprecated it with a different product

                      1 Reply Last reply
                      0
                      • ohmrun@indieweb.socialO ohmrun@indieweb.social

                        @dazfuller That's Tim travelling back in time to fix his morge strategy.

                        leo_wallentin@mastodon.socialL This user is from outside of this forum
                        leo_wallentin@mastodon.socialL This user is from outside of this forum
                        leo_wallentin@mastodon.social
                        wrote last edited by
                        #16

                        @ohmrun @dazfuller to be fair time travel often seems like the most viable option when git merges go wrong

                        1 Reply Last reply
                        0
                        • dazfuller@mstdn.socialD dazfuller@mstdn.social

                          This is truly glorious #AISlop from #Microslop in their "Introduction to Github" course.

                          I don't know why Tim is working in the opposite direction, but I can see that he never once "morges" his code back into develop, let alone doing it "continvoucly"

                          Link Preview Image
                          Components of the GitHub flow - Training

                          Learn to use the components of the GitHub flow

                          favicon

                          (learn.microsoft.com)

                          shadowdancer@mstdn.socialS This user is from outside of this forum
                          shadowdancer@mstdn.socialS This user is from outside of this forum
                          shadowdancer@mstdn.social
                          wrote last edited by
                          #17

                          @dazfuller
                          Now WTF seriously? I had to literally spell the domain out loud. Yes, it really is microsoft.com and not some parody site. It's not like I ever held Microsoft in high regard but this is beyond all comprehension.

                          Is there really no one doing any proofreading anymore? I mean, yeah they're in AI business and they use it themselves, but I wasn't aware they've literally taken hands off the wheel entirely.

                          dazfuller@mstdn.socialD 1 Reply Last reply
                          0
                          • shadowdancer@mstdn.socialS shadowdancer@mstdn.social

                            @dazfuller
                            Now WTF seriously? I had to literally spell the domain out loud. Yes, it really is microsoft.com and not some parody site. It's not like I ever held Microsoft in high regard but this is beyond all comprehension.

                            Is there really no one doing any proofreading anymore? I mean, yeah they're in AI business and they use it themselves, but I wasn't aware they've literally taken hands off the wheel entirely.

                            dazfuller@mstdn.socialD This user is from outside of this forum
                            dazfuller@mstdn.socialD This user is from outside of this forum
                            dazfuller@mstdn.social
                            wrote last edited by
                            #18

                            @shadowdancer I’m sure they said something about quality recently as well 😆

                            Got to admit that I did the same as well. No way, I thought, they would take a well recognised and widely used image and fuck it up with AI. But, alas, this is where we are.

                            They’re now driving around a mountain, perilously close to the edge, blindfolded, and not holding the wheel.

                            1 Reply Last reply
                            0
                            • dazfuller@mstdn.socialD dazfuller@mstdn.social

                              This is truly glorious #AISlop from #Microslop in their "Introduction to Github" course.

                              I don't know why Tim is working in the opposite direction, but I can see that he never once "morges" his code back into develop, let alone doing it "continvoucly"

                              Link Preview Image
                              Components of the GitHub flow - Training

                              Learn to use the components of the GitHub flow

                              favicon

                              (learn.microsoft.com)

                              andrewradev@hachyderm.ioA This user is from outside of this forum
                              andrewradev@hachyderm.ioA This user is from outside of this forum
                              andrewradev@hachyderm.io
                              wrote last edited by
                              #19

                              @dazfuller This, to me, is a perfect encapsulation of the value proposition of chatbots: do what you can already do, but worse.

                              The original image is available on the author's blog as a high-resolution PDF, explicitly licensed as Creative Commons BY-SA. It is *trivial* to find the article and get the canonical image. Instead, somebody asked copilot to regurgitate one, or possibly asked it to "upscale" a low-res copy of it.

                              Doing the work well would have been faster and easier, but the vibe must flow.

                              1 Reply Last reply
                              0
                              • dazfuller@mstdn.socialD dazfuller@mstdn.social

                                @rhempel I mean, it _should_ be gitflow, and yet the AI somehow made it more complicated and incorporated temporal dynamics

                                jsamcfarlane@mastodon.ieJ This user is from outside of this forum
                                jsamcfarlane@mastodon.ieJ This user is from outside of this forum
                                jsamcfarlane@mastodon.ie
                                wrote last edited by
                                #20

                                @dazfuller @rhempel TBF, it's made only slightly worse

                                dazfuller@mstdn.socialD 1 Reply Last reply
                                0
                                • jsamcfarlane@mastodon.ieJ jsamcfarlane@mastodon.ie

                                  @dazfuller @rhempel TBF, it's made only slightly worse

                                  dazfuller@mstdn.socialD This user is from outside of this forum
                                  dazfuller@mstdn.socialD This user is from outside of this forum
                                  dazfuller@mstdn.social
                                  wrote last edited by
                                  #21

                                  @JSAMcFarlane @rhempel I’m sure everyone who loves gitflow will come to its rescue 👀

                                  1 Reply Last reply
                                  0
                                  • dazfuller@mstdn.socialD dazfuller@mstdn.social

                                    This is truly glorious #AISlop from #Microslop in their "Introduction to Github" course.

                                    I don't know why Tim is working in the opposite direction, but I can see that he never once "morges" his code back into develop, let alone doing it "continvoucly"

                                    Link Preview Image
                                    Components of the GitHub flow - Training

                                    Learn to use the components of the GitHub flow

                                    favicon

                                    (learn.microsoft.com)

                                    dpnash@c.imD This user is from outside of this forum
                                    dpnash@c.imD This user is from outside of this forum
                                    dpnash@c.im
                                    wrote last edited by
                                    #22

                                    @dazfuller > don't know why Tim is working in the opposite direction

                                    It's not "Tim", it's "Timn" or "Tinm". No wonder everyone is confused. "Timn" is the one who's working backwards. The *real* Tim, who is working forwards and understands the details of `git morge --continvoucly`, already left for the day. The team will have to settle for a regular old non-continvoucal morge until Tim comes back and they can ask him for help.

                                    dazfuller@mstdn.socialD 1 Reply Last reply
                                    0
                                    • dazfuller@mstdn.socialD dazfuller@mstdn.social

                                      This is truly glorious #AISlop from #Microslop in their "Introduction to Github" course.

                                      I don't know why Tim is working in the opposite direction, but I can see that he never once "morges" his code back into develop, let alone doing it "continvoucly"

                                      Link Preview Image
                                      Components of the GitHub flow - Training

                                      Learn to use the components of the GitHub flow

                                      favicon

                                      (learn.microsoft.com)

                                      tmr232@mastodon.socialT This user is from outside of this forum
                                      tmr232@mastodon.socialT This user is from outside of this forum
                                      tmr232@mastodon.social
                                      wrote last edited by
                                      #23

                                      @dazfuller this is painful...

                                      dazfuller@mstdn.socialD 1 Reply Last reply
                                      0
                                      • dpnash@c.imD dpnash@c.im

                                        @dazfuller > don't know why Tim is working in the opposite direction

                                        It's not "Tim", it's "Timn" or "Tinm". No wonder everyone is confused. "Timn" is the one who's working backwards. The *real* Tim, who is working forwards and understands the details of `git morge --continvoucly`, already left for the day. The team will have to settle for a regular old non-continvoucal morge until Tim comes back and they can ask him for help.

                                        dazfuller@mstdn.socialD This user is from outside of this forum
                                        dazfuller@mstdn.socialD This user is from outside of this forum
                                        dazfuller@mstdn.social
                                        wrote last edited by
                                        #24

                                        @dpnash oh shit, sorry Tim! You should have words with Timn tomorrow before he starts working from the initial commit

                                        jbaggs@infosec.exchangeJ 1 Reply Last reply
                                        0
                                        • tmr232@mastodon.socialT tmr232@mastodon.social

                                          @dazfuller this is painful...

                                          dazfuller@mstdn.socialD This user is from outside of this forum
                                          dazfuller@mstdn.socialD This user is from outside of this forum
                                          dazfuller@mstdn.social
                                          wrote last edited by
                                          #25

                                          @tmr232 this is the future. It’s because we don’t understand how to morge code that software development will be dead in 6-12 months.

                                          Just don’t ask which 6-12 months

                                          1 Reply Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          • Login

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Categories
                                          • Recent
                                          • Tags
                                          • Popular
                                          • World
                                          • Users
                                          • Groups