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.
  • 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
          • 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)

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

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

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

                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)

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

                @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
                • aedius@lavraievie.socialA aedius@lavraievie.social

                  @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 This user is from outside of this forum
                  wila@mastodon.socialW This user is from outside of this forum
                  wila@mastodon.social
                  wrote last edited by
                  #32

                  @Aedius @elizayer there's just going to be less open source

                  aedius@lavraievie.socialA 1 Reply Last reply
                  0
                  • spazcosoft@peoplemaking.gamesS spazcosoft@peoplemaking.games

                    @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 This user is from outside of this forum
                    waldi@chaos.socialW This user is from outside of this forum
                    waldi@chaos.social
                    wrote last edited by
                    #33

                    @spazcosoft @elizayer Wasn't this always? Newly hyped stuff is used for scam, or porn, or both.

                    1 Reply Last reply
                    0
                    • wila@mastodon.socialW wila@mastodon.social

                      @Aedius @elizayer there's just going to be less open source

                      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
                      #34

                      @wila @elizayer

                      All code is open source when you push it with a map file.

                      wila@mastodon.socialW 1 Reply Last reply
                      0
                      • aedius@lavraievie.socialA aedius@lavraievie.social

                        @wila @elizayer

                        All code is open source when you push it with a map file.

                        wila@mastodon.socialW This user is from outside of this forum
                        wila@mastodon.socialW This user is from outside of this forum
                        wila@mastodon.social
                        wrote last edited by
                        #35

                        @Aedius @elizayer when it is javascript yes.
                        I wasn't talking about less slop.
                        There will be more of that.

                        1 Reply Last reply
                        0
                        • robtherunt@cupoftea.socialR This user is from outside of this forum
                          robtherunt@cupoftea.socialR This user is from outside of this forum
                          robtherunt@cupoftea.social
                          wrote last edited by
                          #36

                          @macronencer @mroach @elizayer
                          When I was working, I would regularly solve a development issue while in the shower. I think it’s the brain being unstressed that does that.

                          mroach@ublog.mroach.comM 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.

                            ulveon@derg.socialU This user is from outside of this forum
                            ulveon@derg.socialU This user is from outside of this forum
                            ulveon@derg.social
                            wrote last edited by
                            #37

                            @elizayer@mastodon.social Claude Code found a 23-year-old Linux vulnerability, the kind a regular human security auditor would have taken weeks or months to find (or in this case, 23 years). https://mtlynch.io/claude-code-found-linux-vulnerability/

                            diekehrseite@mastodon.socialD 1 Reply Last reply
                            0
                            • robtherunt@cupoftea.socialR robtherunt@cupoftea.social

                              @macronencer @mroach @elizayer
                              When I was working, I would regularly solve a development issue while in the shower. I think it’s the brain being unstressed that does that.

                              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
                              #38

                              @robtherunt @macronencer @elizayer Same! I’ve half jokingly said my bathroom is the most productive room in my home office setup. Sitting on the toilet and lots of a-ha moments

                              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)

                                joeslow@me.dmJ This user is from outside of this forum
                                joeslow@me.dmJ This user is from outside of this forum
                                joeslow@me.dm
                                wrote last edited by
                                #39

                                @elizayer @trendytoots I can very much relate to this

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

                                  So why are we still trying to optimize code creation?

                                  For decades, people with power - executives and product people - have been shifting the blame for strategy failures and poor market insight onto development "productivity."

                                  This AI moment should be incredibly clarifying. Like, it should be the reductio ad absurdum of a productivity-centric approach.

                                  elrohir@mastodon.galE This user is from outside of this forum
                                  elrohir@mastodon.galE This user is from outside of this forum
                                  elrohir@mastodon.gal
                                  wrote last edited by
                                  #40

                                  @elizayer management blame productivity for strategy failure because their approach to strategy path-finding is flooding: say a bunch of random hunches overconfidently, make teams try different things out for a little while, see what sticks. They see making code faster not as a way to manufacture a good design more efficiently, but as a means to generate management fuck ups and backpedals at faster pace and greater scale.

                                  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.

                                    nienkez@mastodon.nlN This user is from outside of this forum
                                    nienkez@mastodon.nlN This user is from outside of this forum
                                    nienkez@mastodon.nl
                                    wrote last edited by
                                    #41

                                    @elizayer @ArtHarg AI only solves one problem: paying people wages.

                                    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.

                                      diekehrseite@mastodon.socialD This user is from outside of this forum
                                      diekehrseite@mastodon.socialD This user is from outside of this forum
                                      diekehrseite@mastodon.social
                                      wrote last edited by
                                      #42

                                      @elizayer word!

                                      1 Reply Last reply
                                      0
                                      • ulveon@derg.socialU ulveon@derg.social

                                        @elizayer@mastodon.social Claude Code found a 23-year-old Linux vulnerability, the kind a regular human security auditor would have taken weeks or months to find (or in this case, 23 years). https://mtlynch.io/claude-code-found-linux-vulnerability/

                                        diekehrseite@mastodon.socialD This user is from outside of this forum
                                        diekehrseite@mastodon.socialD This user is from outside of this forum
                                        diekehrseite@mastodon.social
                                        wrote last edited by
                                        #43

                                        @ulveon so this case justifies bazillions of dollars to be invested in needless serverfarms? And if that vulnerability wasnt discovered for 23 years it was prolly so well hidden that it was not an issue at all. Think about it.

                                        @elizayer

                                        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)

                                          arcadiagt5@mstdn.socialA This user is from outside of this forum
                                          arcadiagt5@mstdn.socialA This user is from outside of this forum
                                          arcadiagt5@mstdn.social
                                          wrote last edited by
                                          #44

                                          @elizayer And very well said it is!

                                          This is why #BusinessAnalysts exist, or SHOULD exist.

                                          To talk to your users and THEN to tell your coders what to build AND WHY.

                                          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