Skip to content
  • Hjem
  • Seneste
  • Etiketter
  • Populære
  • Verden
  • Bruger
  • Grupper
Temaer
  • 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 (No Skin)
  • No Skin
Kollaps
FARVEL BIG TECH
  1. Forside
  2. Ikke-kategoriseret
  3. I'm a big fan of this explanation/rant from Andrew Murphy.

I'm a big fan of this explanation/rant from Andrew Murphy.

Planlagt Fastgjort Låst Flyttet Ikke-kategoriseret
94 Indlæg 59 Posters 0 Visninger
  • Ældste til nyeste
  • Nyeste til ældste
  • Most Votes
Svar
  • Svar som emne
Login for at svare
Denne tråd er blevet slettet. Kun brugere med emne behandlings privilegier kan se den.
  • elizayer@mastodon.socialE elizayer@mastodon.social

    The fact that we are *not* seeing wildly improving software all around us tells us everything we need to know.

    There is no flourishing of value delivery, new product categories, more needs being satisfied better. It’s the opposite.

    All we are seeing is decreases in quality, because 👏 code 👏 creation 👏 is not 👏 the problem.

    aedius@lavraievie.socialA This user is from outside of this forum
    aedius@lavraievie.socialA This user is from outside of this forum
    aedius@lavraievie.social
    wrote sidst redigeret af
    #12

    @elizayer

    The good news is :

    Open source maintainers see an increase in the quality of AI security tools, it will soon be in the hands of the bad actors.

    Then it will be mandatory to do good software and ( i will make the leap of faith that ) you have to understand the business needs to create a simple software that handle the issues.

    wila@mastodon.socialW joeinwynnewood@mstdn.socialJ 2 Replies Last reply
    0
    • elizayer@mastodon.socialE elizayer@mastodon.social

      @BmeBenji @beep

      I generally agree!

      On the narrow Waymo point, a few things have made me reconsider recently:

      - Cyclists who feel Waymos are more predictable and less likely to make the equivalent of attentiveness mistakes. Or to be actively hostile.

      - Women and older people who've said they feel vulnerable alone in a car with a driver.

      niall@mastodon.nzN This user is from outside of this forum
      niall@mastodon.nzN This user is from outside of this forum
      niall@mastodon.nz
      wrote sidst redigeret af
      #13

      @elizayer @BmeBenji @beep also folks with impairments meaning they can't drive. This is a great piece of podcast journalism about the response to Waymo applying to operate in Chicago:
      https://pca.st/episode/ef4a328f-dbd4-45cb-8a0b-985250d62293

      beep@follow.ethanmarcotte.comB 1 Reply Last reply
      0
      • elizayer@mastodon.socialE elizayer@mastodon.social

        The fact that we are *not* seeing wildly improving software all around us tells us everything we need to know.

        There is no flourishing of value delivery, new product categories, more needs being satisfied better. It’s the opposite.

        All we are seeing is decreases in quality, because 👏 code 👏 creation 👏 is not 👏 the problem.

        cap_ybarra@beige.partyC This user is from outside of this forum
        cap_ybarra@beige.partyC This user is from outside of this forum
        cap_ybarra@beige.party
        wrote sidst redigeret af
        #14

        @elizayer this has never been about quality and only about the business class trying to free themselves from those damned uppity engineers

        1 Reply Last reply
        0
        • elizayer@mastodon.socialE elizayer@mastodon.social

          The fact that we are *not* seeing wildly improving software all around us tells us everything we need to know.

          There is no flourishing of value delivery, new product categories, more needs being satisfied better. It’s the opposite.

          All we are seeing is decreases in quality, because 👏 code 👏 creation 👏 is not 👏 the problem.

          mroach@ublog.mroach.comM This user is from outside of this forum
          mroach@ublog.mroach.comM This user is from outside of this forum
          mroach@ublog.mroach.com
          wrote sidst redigeret af
          #15

          @elizayer Exactly! I’ve been trying to explain to people, especially those pushing AI at work, that writing code is not the hard part of my job. Identifying the real-world problems and designing solutions that are as minimalist and simple as possible are the hard parts. The code is an implementation detail.

          macronencer@mastodon.scotM 1 Reply Last reply
          0
          • elizayer@mastodon.socialE elizayer@mastodon.social

            I'm a big fan of this explanation/rant from Andrew Murphy.

            Taken as a whole, there are many bottlenecks in a corporate software development process. The "load-bearing" calendar is a great example!

            Speeding up code creation just increases pressure on the bottleneck, which decreases throughput.

            https://andrewmurphy.io/blog/if-you-thought-the-speed-of-writing-code-was-your-problem-you-have-bigger-problems

            mtnrbq65@social.vivaldi.netM This user is from outside of this forum
            mtnrbq65@social.vivaldi.netM This user is from outside of this forum
            mtnrbq65@social.vivaldi.net
            wrote sidst redigeret af
            #16

            @elizayer

            Absolutely:
            "More code, less understanding. That's not a productivity gain. That's a time bomb with a nicer dashboard."

            aeischeid@mastodon.socialA 1 Reply Last reply
            0
            • elizayer@mastodon.socialE elizayer@mastodon.social

              I'm a big fan of this explanation/rant from Andrew Murphy.

              Taken as a whole, there are many bottlenecks in a corporate software development process. The "load-bearing" calendar is a great example!

              Speeding up code creation just increases pressure on the bottleneck, which decreases throughput.

              https://andrewmurphy.io/blog/if-you-thought-the-speed-of-writing-code-was-your-problem-you-have-bigger-problems

              neverpanic@chaos.socialN This user is from outside of this forum
              neverpanic@chaos.socialN This user is from outside of this forum
              neverpanic@chaos.social
              wrote sidst redigeret af
              #17

              @elizayer @sophieschmieg The CEO of Tailscale made that same point a few weeks ago on their personal blog at https://apenwarr.ca/log/20260316. This is so true, and every initiative to accelerate delivery with LLMs should really focus on these things first instead.

              1 Reply Last reply
              0
              • elizayer@mastodon.socialE elizayer@mastodon.social

                I'm a big fan of this explanation/rant from Andrew Murphy.

                Taken as a whole, there are many bottlenecks in a corporate software development process. The "load-bearing" calendar is a great example!

                Speeding up code creation just increases pressure on the bottleneck, which decreases throughput.

                https://andrewmurphy.io/blog/if-you-thought-the-speed-of-writing-code-was-your-problem-you-have-bigger-problems

                hoolis@oldbytes.spaceH This user is from outside of this forum
                hoolis@oldbytes.spaceH This user is from outside of this forum
                hoolis@oldbytes.space
                wrote sidst redigeret af
                #18

                @elizayer Tragically, many of my colleagues are now concluding the solution is to have the same tool that produced the code review the code, as a way to manage the bottleneck.

                I think it's something in the water.

                1 Reply Last reply
                0
                • elizayer@mastodon.socialE elizayer@mastodon.social

                  The fact that we are *not* seeing wildly improving software all around us tells us everything we need to know.

                  There is no flourishing of value delivery, new product categories, more needs being satisfied better. It’s the opposite.

                  All we are seeing is decreases in quality, because 👏 code 👏 creation 👏 is not 👏 the problem.

                  spazcosoft@peoplemaking.gamesS This user is from outside of this forum
                  spazcosoft@peoplemaking.gamesS This user is from outside of this forum
                  spazcosoft@peoplemaking.games
                  wrote sidst redigeret af
                  #19

                  @elizayer to be 100% completely super fair, we are seeing a massive increase in scams. So AI is good for something. Scams. It’s good for scams.

                  waldi@chaos.socialW 1 Reply Last reply
                  0
                  • niall@mastodon.nzN niall@mastodon.nz

                    @elizayer @BmeBenji @beep also folks with impairments meaning they can't drive. This is a great piece of podcast journalism about the response to Waymo applying to operate in Chicago:
                    https://pca.st/episode/ef4a328f-dbd4-45cb-8a0b-985250d62293

                    beep@follow.ethanmarcotte.comB This user is from outside of this forum
                    beep@follow.ethanmarcotte.comB This user is from outside of this forum
                    beep@follow.ethanmarcotte.com
                    wrote sidst redigeret af
                    #20

                    @Niall @elizayer While I haven’t listened to the episode — I didn’t realize Pinnamaneni and Vogt had a new project, after the Gimlet debacle — I can say the accessibility question here in Boston is much, much more complicated than that.

                    niall@mastodon.nzN 1 Reply Last reply
                    0
                    • elizayer@mastodon.socialE elizayer@mastodon.social

                      I'm a big fan of this explanation/rant from Andrew Murphy.

                      Taken as a whole, there are many bottlenecks in a corporate software development process. The "load-bearing" calendar is a great example!

                      Speeding up code creation just increases pressure on the bottleneck, which decreases throughput.

                      https://andrewmurphy.io/blog/if-you-thought-the-speed-of-writing-code-was-your-problem-you-have-bigger-problems

                      mogul@hachyderm.ioM This user is from outside of this forum
                      mogul@hachyderm.ioM This user is from outside of this forum
                      mogul@hachyderm.io
                      wrote sidst redigeret af
                      #21

                      @elizayer We're gonna need a bigger Theory of Constraints.

                      1 Reply Last reply
                      0
                      • elizayer@mastodon.socialE elizayer@mastodon.social

                        I'm a big fan of this explanation/rant from Andrew Murphy.

                        Taken as a whole, there are many bottlenecks in a corporate software development process. The "load-bearing" calendar is a great example!

                        Speeding up code creation just increases pressure on the bottleneck, which decreases throughput.

                        https://andrewmurphy.io/blog/if-you-thought-the-speed-of-writing-code-was-your-problem-you-have-bigger-problems

                        alanxoc3@tilde.zoneA This user is from outside of this forum
                        alanxoc3@tilde.zoneA This user is from outside of this forum
                        alanxoc3@tilde.zone
                        wrote sidst redigeret af
                        #22

                        @elizayer Very very true.

                        1 Reply Last reply
                        0
                        • elizayer@mastodon.socialE elizayer@mastodon.social

                          The fact that we are *not* seeing wildly improving software all around us tells us everything we need to know.

                          There is no flourishing of value delivery, new product categories, more needs being satisfied better. It’s the opposite.

                          All we are seeing is decreases in quality, because 👏 code 👏 creation 👏 is not 👏 the problem.

                          kirakira@furry.engineerK This user is from outside of this forum
                          kirakira@furry.engineerK This user is from outside of this forum
                          kirakira@furry.engineer
                          wrote sidst redigeret af
                          #23

                          @elizayer i think about this. according to the promises, all the little snags and bugs and oversights in all the software i use should be gone by now. "everyone's focusing on bigger things" doesn't excuse it, i was given the expectation these types of fixes should have been trivial and quick. computing should be better than ever, or at least as good as it was in the 2010s

                          1 Reply Last reply
                          0
                          • beep@follow.ethanmarcotte.comB beep@follow.ethanmarcotte.com

                            @Niall @elizayer While I haven’t listened to the episode — I didn’t realize Pinnamaneni and Vogt had a new project, after the Gimlet debacle — I can say the accessibility question here in Boston is much, much more complicated than that.

                            niall@mastodon.nzN This user is from outside of this forum
                            niall@mastodon.nzN This user is from outside of this forum
                            niall@mastodon.nz
                            wrote sidst redigeret af
                            #24

                            @beep @elizayer well yes, it's clear you haven't listened to the episode 😉

                            gunchleoc@mastodon.scotG 1 Reply Last reply
                            0
                            • elizayer@mastodon.socialE elizayer@mastodon.social

                              I'm a big fan of this explanation/rant from Andrew Murphy.

                              Taken as a whole, there are many bottlenecks in a corporate software development process. The "load-bearing" calendar is a great example!

                              Speeding up code creation just increases pressure on the bottleneck, which decreases throughput.

                              https://andrewmurphy.io/blog/if-you-thought-the-speed-of-writing-code-was-your-problem-you-have-bigger-problems

                              nickrauchen@c.imN This user is from outside of this forum
                              nickrauchen@c.imN This user is from outside of this forum
                              nickrauchen@c.im
                              wrote sidst redigeret af
                              #25

                              @elizayer

                              "The Mythical Man Month"

                              https://en.wikipedia.org/wiki/The_Mythical_Man-Month

                              1 Reply Last reply
                              0
                              • mtnrbq65@social.vivaldi.netM mtnrbq65@social.vivaldi.net

                                @elizayer

                                Absolutely:
                                "More code, less understanding. That's not a productivity gain. That's a time bomb with a nicer dashboard."

                                aeischeid@mastodon.socialA This user is from outside of this forum
                                aeischeid@mastodon.socialA This user is from outside of this forum
                                aeischeid@mastodon.social
                                wrote sidst redigeret af
                                #26

                                @mtnrbq65 @elizayer developers sometimes reference the 80/20 rule. And let's say in certain ways LLM code tools can get you through that 80% part faster, but they also have very real risk of making the last 20% even slower.

                                1 Reply Last reply
                                0
                                • elizayer@mastodon.socialE elizayer@mastodon.social

                                  The fact that we are *not* seeing wildly improving software all around us tells us everything we need to know.

                                  There is no flourishing of value delivery, new product categories, more needs being satisfied better. It’s the opposite.

                                  All we are seeing is decreases in quality, because 👏 code 👏 creation 👏 is not 👏 the problem.

                                  wbftw@hachyderm.ioW This user is from outside of this forum
                                  wbftw@hachyderm.ioW This user is from outside of this forum
                                  wbftw@hachyderm.io
                                  wrote sidst redigeret af
                                  #27

                                  @elizayer yes, this. Code creation hasn’t been an issue for a long, long, long time. See “no silver bullet” (https://worrydream.com/refs/Brooks_1986_-_No_Silver_Bullet.pdf) written in *1986*.

                                  1 Reply Last reply
                                  0
                                  • elizayer@mastodon.socialE elizayer@mastodon.social

                                    I'm a big fan of this explanation/rant from Andrew Murphy.

                                    Taken as a whole, there are many bottlenecks in a corporate software development process. The "load-bearing" calendar is a great example!

                                    Speeding up code creation just increases pressure on the bottleneck, which decreases throughput.

                                    https://andrewmurphy.io/blog/if-you-thought-the-speed-of-writing-code-was-your-problem-you-have-bigger-problems

                                    standard_phil@infosec.exchangeS This user is from outside of this forum
                                    standard_phil@infosec.exchangeS This user is from outside of this forum
                                    standard_phil@infosec.exchange
                                    wrote sidst redigeret af
                                    #28

                                    @elizayer I've listened to a few podcasts now where software company executives (and even a CEO, who I would have expected to know better because he's a CEO) have talked about how much faster their teams are producing code, and since their QA teams can't keep up they've fired those people and are using Claude for QA now.

                                    I get that devs don't study management subjects (I was one myself, many years ago) so they won't necessarily know how to find and fix bottlenecks, but I'm genuinely disappointed that software industry executives don't realise they're in a manufacturing business, nor do they understand how to optimise their value chains.

                                    I know it's a cliche to say that people fail upwards, and I've worked with many executives who were clearly in their roles because they were intelligent, educated, and were delivering at a strategic level - but I'm beginning to wonder if software businesses are a special case.

                                    1 Reply Last reply
                                    0
                                    • elizayer@mastodon.socialE elizayer@mastodon.social

                                      The fact that we are *not* seeing wildly improving software all around us tells us everything we need to know.

                                      There is no flourishing of value delivery, new product categories, more needs being satisfied better. It’s the opposite.

                                      All we are seeing is decreases in quality, because 👏 code 👏 creation 👏 is not 👏 the problem.

                                      guitarsith@fosstodon.orgG This user is from outside of this forum
                                      guitarsith@fosstodon.orgG This user is from outside of this forum
                                      guitarsith@fosstodon.org
                                      wrote sidst redigeret af
                                      #29

                                      @elizayer
                                      Almost all of the code written by the major software companies since the late 80’s has been bloatware. Especially operating systems. The days when programming was an art and minimizing resource usage was the primary consideration are long gone. If that code is what AI and these LLM’s are being “trained” on then expect software to continue its downward spiral.

                                      1 Reply Last reply
                                      0
                                      • elizayer@mastodon.socialE elizayer@mastodon.social

                                        I'm a big fan of this explanation/rant from Andrew Murphy.

                                        Taken as a whole, there are many bottlenecks in a corporate software development process. The "load-bearing" calendar is a great example!

                                        Speeding up code creation just increases pressure on the bottleneck, which decreases throughput.

                                        https://andrewmurphy.io/blog/if-you-thought-the-speed-of-writing-code-was-your-problem-you-have-bigger-problems

                                        mjt@mastodon.onlineM This user is from outside of this forum
                                        mjt@mastodon.onlineM This user is from outside of this forum
                                        mjt@mastodon.online
                                        wrote sidst redigeret af
                                        #30

                                        @elizayer This is a fabulously well-written article on flow, constraints, and fixing the biggest constraint first. Well worth nyour time if you do…well, anything.

                                        1 Reply Last reply
                                        0
                                        • niall@mastodon.nzN niall@mastodon.nz

                                          @beep @elizayer well yes, it's clear you haven't listened to the episode 😉

                                          gunchleoc@mastodon.scotG This user is from outside of this forum
                                          gunchleoc@mastodon.scotG This user is from outside of this forum
                                          gunchleoc@mastodon.scot
                                          wrote sidst redigeret af
                                          #31

                                          @Niall @beep @elizayer Germans have a word for accessible cars. it translates as "low floor bus". Sorry, there's no English language version of that article https://de.wikipedia.org/wiki/Niederflurtechnik

                                          Of course, there are people whose disability doesn't allow them to take a bus, those will need a driving service.

                                          Also, driverless subways make a lot more sense than driverless cars, because you have a much more controlled environment.

                                          1 Reply Last reply
                                          0
                                          Svar
                                          • Svar som emne
                                          Login for at svare
                                          • Ældste til nyeste
                                          • Nyeste til ældste
                                          • Most Votes


                                          • Log ind

                                          • Har du ikke en konto? Tilmeld

                                          • Login or register to search.
                                          Powered by NodeBB Contributors
                                          Graciously hosted by data.coop
                                          • First post
                                            Last post
                                          0
                                          • Hjem
                                          • Seneste
                                          • Etiketter
                                          • Populære
                                          • Verden
                                          • Bruger
                                          • Grupper