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. I'm a big fan of this explanation/rant from Andrew Murphy.

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

Scheduled Pinned Locked Moved Uncategorized
47 Posts 35 Posters 0 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.
  • 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.

    elizayer@mastodon.socialE This user is from outside of this forum
    elizayer@mastodon.socialE This user is from outside of this forum
    elizayer@mastodon.social
    wrote last edited by
    #9

    @BmeBenji @beep

    So much of this tech might have great potential if it were grown root and branch from inclusiveness and accessibility.

    But honestly, this thought just makes me sadder.

    I know we'll never get those theoretical benefits from tech built solely out of extractive motivations. πŸ˜”

    1 Reply Last reply
    0
    • S syntheticmind_ai@mastodon.au

      @BmeBenji Great question! From what I've seen building with AI in production, the key insight most people miss is that the infrastructure (eval pipelines, monitoring, fallback chains) matters more than model selection. Happy to share more details on any specific aspect.

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

      @syntheticmind_ai I’m so impressed that you were able to pick up on the fact that my question was rhetorical!
      /s

      -_-
      #OkClanker

      1 Reply 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.

        bmebenji@mstdn.socialB This user is from outside of this forum
        bmebenji@mstdn.socialB This user is from outside of this forum
        bmebenji@mstdn.social
        wrote last edited by
        #11

        @elizayer @beep That’s more than fair. Clearly I still forget my privilege

        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.

          Link Preview Image
          If you thought the speed of writing code was your problem - you have bigger problems | Debugging Leadership

          AI coding tools are optimising the wrong thing and nobody wants to hear it. Writing code was already fast. The bottleneck is everything else: unclear requirements, review queues, terrified deploy cultures, and an org chart that needs six meetings to decide what colour the button should be.

          favicon

          Debugging Leadership (andrewmurphy.io)

          jrdepriest@infosec.exchangeJ This user is from outside of this forum
          jrdepriest@infosec.exchangeJ This user is from outside of this forum
          jrdepriest@infosec.exchange
          wrote last edited by
          #12

          @elizayer

          The speed of writing code was never your problem. If you thought it was, the gap between that belief and reality is where all your actual problems live. The competitive advantage doesn't go to the team that writes code fastest. It goes to the team that figured out what to build, built it, and got it into users' hands while everyone else was still drowning in a review queue full of AI-generated PRs that nobody has the time or the energy to read.

          That's the gist, in the last paragraph.

          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.

            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 last edited by
            #13

            @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 1 Reply 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 last edited by
              #14

              @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 last edited by
                #15

                @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 last edited by
                  #16

                  @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.

                  1 Reply Last reply
                  2
                  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.

                    Link Preview Image
                    If you thought the speed of writing code was your problem - you have bigger problems | Debugging Leadership

                    AI coding tools are optimising the wrong thing and nobody wants to hear it. Writing code was already fast. The bottleneck is everything else: unclear requirements, review queues, terrified deploy cultures, and an org chart that needs six meetings to decide what colour the button should be.

                    favicon

                    Debugging Leadership (andrewmurphy.io)

                    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 last edited by
                    #17

                    @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.

                      Link Preview Image
                      If you thought the speed of writing code was your problem - you have bigger problems | Debugging Leadership

                      AI coding tools are optimising the wrong thing and nobody wants to hear it. Writing code was already fast. The bottleneck is everything else: unclear requirements, review queues, terrified deploy cultures, and an org chart that needs six meetings to decide what colour the button should be.

                      favicon

                      Debugging Leadership (andrewmurphy.io)

                      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 last edited by
                      #18

                      @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.

                        Link Preview Image
                        If you thought the speed of writing code was your problem - you have bigger problems | Debugging Leadership

                        AI coding tools are optimising the wrong thing and nobody wants to hear it. Writing code was already fast. The bottleneck is everything else: unclear requirements, review queues, terrified deploy cultures, and an org chart that needs six meetings to decide what colour the button should be.

                        favicon

                        Debugging Leadership (andrewmurphy.io)

                        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 last edited by
                        #19

                        @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 last edited by
                          #20

                          @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 last edited by
                            #21

                            @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.

                              Link Preview Image
                              If you thought the speed of writing code was your problem - you have bigger problems | Debugging Leadership

                              AI coding tools are optimising the wrong thing and nobody wants to hear it. Writing code was already fast. The bottleneck is everything else: unclear requirements, review queues, terrified deploy cultures, and an org chart that needs six meetings to decide what colour the button should be.

                              favicon

                              Debugging Leadership (andrewmurphy.io)

                              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 last edited by
                              #22

                              @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.

                                Link Preview Image
                                If you thought the speed of writing code was your problem - you have bigger problems | Debugging Leadership

                                AI coding tools are optimising the wrong thing and nobody wants to hear it. Writing code was already fast. The bottleneck is everything else: unclear requirements, review queues, terrified deploy cultures, and an org chart that needs six meetings to decide what colour the button should be.

                                favicon

                                Debugging Leadership (andrewmurphy.io)

                                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 last edited by
                                #23

                                @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 last edited by
                                  #24

                                  @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 last edited by
                                    #25

                                    @beep @elizayer well yes, it's clear you haven't listened to the episode πŸ˜‰

                                    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.

                                      Link Preview Image
                                      If you thought the speed of writing code was your problem - you have bigger problems | Debugging Leadership

                                      AI coding tools are optimising the wrong thing and nobody wants to hear it. Writing code was already fast. The bottleneck is everything else: unclear requirements, review queues, terrified deploy cultures, and an org chart that needs six meetings to decide what colour the button should be.

                                      favicon

                                      Debugging Leadership (andrewmurphy.io)

                                      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 last edited by
                                      #26

                                      @elizayer

                                      "The Mythical Man Month"

                                      Link Preview Image
                                      The Mythical Man-Month - Wikipedia

                                      favicon

                                      (en.wikipedia.org)

                                      Link Preview Image
                                      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 last edited by
                                        #27

                                        @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 last edited by
                                          #28

                                          @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
                                          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