[HN Gopher] Just Build It...
       ___________________________________________________________________
        
       Just Build It...
        
       Author : weird_science
       Score  : 11 points
       Date   : 2023-09-03 11:08 UTC (1 days ago)
        
 (HTM) web link (blog.stephaniestimac.com)
 (TXT) w3m dump (blog.stephaniestimac.com)
        
       | kingforaday wrote:
       | _" One group is instructed to submit 100 photos over the quarter
       | and the other group is instructed to submit one perfect photo.
       | 
       | The group that is instructed to submit 100 photos gets better
       | because they start right away and start taking photos and learn
       | about composition. While the other group doesn't get better
       | because they hem and haw over what a perfect photo is."_
       | 
       | If true, I would want a refund if placed in the latter group.
        
         | brailsafe wrote:
         | Ironically, this is also the downfall of most "agile"
         | practicing dev teams. They've adopted scrum, they've adopted
         | all the overhead of Jira and 2 week sprints that they never
         | rethink, but nothing gets shipped unless it's perfect, and so
         | nothing gets iterated on, nothing progresses, no evaluation of
         | the work ever actually feeds back into a positive reinforcement
         | cycle, and so you just get waterfall with much more agony.
         | 
         | In my last company, we trying to ship refactors and
         | improvements at the same time, and it inevitably broke down
         | horribly when we'd discover some requirement that had
         | originally never been documented or built in some component. So
         | the scope for shipping would change from a one-to-one refactor
         | with incremental iteration in subsequent sprints, to many
         | cycles of QA and fixes before even minor design improvements
         | could be shipped.
         | 
         | It's characteristic of every dev team I've been on that's tried
         | to use off-the-shelf agile practices, because there's no risk
         | tolerance at any level higher than IC. Everyone's afraid of how
         | they'll appear, and nobody trusts anyone lower than them on the
         | org-chart.
        
           | teeray wrote:
           | > nothing gets shipped unless it's perfect, and so nothing
           | gets iterated on...
           | 
           | That's why a solid, painless, quick rollback story is
           | absolutely vital but underrated for agility. It's not a big
           | deal if you ship a regression but can roll back quickly. On
           | the other hand, if every release is playing for keeps, you'll
           | slow down to a glacial pace to try to ship perfection. But
           | perfection is impossible no matter how much process you put
           | in front of it--you _will_ ship a bug some day. So pretending
           | like you can't ship bugs because you have initial design
           | reviews, multiple code reviews, sign-offs from multiple
           | stakeholders, CI that takes 3 days to run, etc. just makes
           | the day you do ship a big that much more painful.
        
       ___________________________________________________________________
       (page generated 2023-09-04 23:00 UTC)