[HN Gopher] Shift Left Software Development Process (2022)
       ___________________________________________________________________
        
       Shift Left Software Development Process (2022)
        
       Author : thunderbong
       Score  : 15 points
       Date   : 2023-11-08 08:10 UTC (14 hours ago)
        
 (HTM) web link (devopedia.org)
 (TXT) w3m dump (devopedia.org)
        
       | datadrivenangel wrote:
       | At the extreme, shifting left becomes BFD: Bug Free Development.
       | Just write correct software at the beginning.
        
       | swader999 wrote:
       | This is just a new name for practices that have been in place for
       | at least twenty years on decent projects. See fail fast, test
       | early, small features, frequent early feedback, anti-pipeline
       | pattern...
        
         | repelsteeltje wrote:
         | And it isn't even _new_. I think I heard the term at least 5
         | years, and I don 't work in a particularly fast moving area of
         | software development.
        
           | drewcoo wrote:
           | https://www.drdobbs.com/shift-left-testing/184404768
           | 
           | That's 2001.
        
             | swader999 wrote:
             | Ok that's hilarious!
        
         | swatcoder wrote:
         | Because we still have no licensing body in software engineering
         | (and I like that), the exponential growth of hiring during
         | industry booms means that many teams are working with _very_
         | thin access to historical knowledge because there are zero or
         | few "old timers" around to convey past technique.
         | 
         | The new generation inevitably reinvents practices and sometimes
         | resurfaces them through independent archaeology, and so there's
         | a lot of cyclical repetition of both successes and failures.
         | There's also sometimes lucky innovations when old ideas get
         | aired out in a new context and yield different results than in
         | the past.
         | 
         | If you've been around for a while, it's easy to call out these
         | repetitions and it can be satisfying to do so. But at the same
         | time, it often means that the new generation is _finally_
         | catching up on things that nobody's been around to teach them.
         | That's something worth celebrating, not diminishing.
        
           | woleium wrote:
           | Well said :)
        
         | gustavus wrote:
         | Ya, after a while in the field I noticed that Xtreme
         | Programming, Agile, DevOps, and now Shift Left, and most other
         | ideas are all just describing the exact same thing. Be flexible
         | in your work, set up your processes to be able to deliver
         | quickly so you can adjust quickly.
         | 
         | I was puzzled why it seemed we were learning the same lessons
         | in an industry over and over again, and why we kept giving new
         | names to things that we're already existing. Then I received
         | enlightenment when I realized that consultants that were
         | selling agile previously were now selling DevOps. The reason
         | they keep changing the name is because it allows consultants to
         | come in and charge you more money to tell you to do the same
         | things management bungled the last 3 times, because the problem
         | isn't with the business processes it's with the idiots running
         | the company.
         | 
         | Or to quote Scott Adams "If you notice a lot of focus on
         | process improvement at your business that's a sign all the
         | smart people have left and management is trying to figure out a
         | process simple enough for the idiots left."
        
       | EarlKing wrote:
       | Aaaaaaaaaand it's hugged to death. And there's no archive.is.
       | Well, have an archive.org link:
       | https://web.archive.org/web/20230202105734/https://devopedia...
        
       | ReactiveJelly wrote:
       | I'd thought of this as similar to Kanban or Test-Driven
       | Development.
       | 
       | Before you start designing, look at what you have and ask why it
       | doesn't already work. Those answers become manual test cases.
       | Then get it into a test environment immediately, not after more
       | than a day of coding. Every day make the test environment more
       | like production. Run the whole cycle every time, build, release,
       | test, otherwise one of the phases will go astray when you aren't
       | exercising it.
       | 
       | I know Kanban is something different but these are all "Don't
       | push from the start of the pipe, pull from the end of the pipe"
       | approaches. It also works with media encoding and decoding. If
       | you push, the buffers fill up and you have to figure out where to
       | stuff packets when the codecs tell you they're full. If you pull,
       | you waste 1 cycle figuring out where to start, but then
       | everything is smooth and just-in-time.
       | 
       | It's all the same crap. It's Lean, too. There must be 20 names
       | for this concept.
        
       | harrylove wrote:
       | Toyoda Automatic Loom Works had the jidoka system which
       | automatically stopped the loom when a thread broke[0] preventing
       | downstream production issues. Later used in the Toyota Production
       | System.
       | 
       | 0. https://en.m.wikipedia.org/wiki/Sakichi_Toyoda
        
       | verdverm wrote:
       | Should it be "shift right" for RTL cultures?
        
       ___________________________________________________________________
       (page generated 2023-11-08 23:00 UTC)