Comments by "Lee Rothman" (@leesoftwareengineer) on "Continuous Delivery" channel.

  1. The main points here covers canary deployments which would have stopped the deployment to most of the 8.5m affected devices. Further information shows that the fault was with one of the data files containing nothing but 0’s. There is no validation of the inputs to the kernel code so it crashed. I’d say that it was most definitely a fault on their part and easily avoided.
    1
  2. Read the state of DevOps report. There is a correlation between the bigger the size of change that is deployed the bigger the failure rate.
    1
  3. ‘Agile project managers’ sounds like an oxymoron to me 😀.
    1
  4.  @Storytelless  You’ll never get the early feedback by testing after. Your design will have already been done by then. You’ll never be 100% sure that you’ve covered all scenarios by testing after either, a coverage tool will only tell you if a test executes a line not that anything is asserted. One other drawback is that if you’ve never seen your test fail how can you be sure it’s correct?
    1
  5.  @SteveBurnap Yup agreed. Have monitoring calling every x seconds to check that it’s getting a successful response.
    1
  6. Shouldn’t acceptance criteria be agreed on before a user story is worked on? Otherwise your going to be writing something that the user doesn’t want? I also don’t really think that the users really cares about the implementation either. With TDD you are running the code to see if it works, that’s what the tests do! How else are you running it? Though a UI and a debugger? That just slows you down.
    1
  7. I just caught up with his update, definitely worth a watch to understand what’s going on with software running on the low level.
    1
  8.  @carstenbohme8813 It’s a fair challenge. Teams get a chance to change their ways of working at the retrospective meeting and frequently modify things, but abandoning TDD hasn’t been suggested.
    1
  9. It could have yes. Initial deployment should have been a small amount of customers. It’s easy to set up monitoring so an external systems checks something like a health check endpoint. If it doesn’t get a successful response then something has gone wrong and stop all further deployments.
    1
  10. That sounds like an opinion based argument rather than a data based argument to me. Start capturing story cycle time with and without TDD and you'll have the data you need.
    1
  11.  @krumbergify  What are these bugs you speak of?
    1
  12. Maybe those details should be linked to the story that it was committed against?
    1
  13.  @alexaneals8194 I’d say it was common practice to link every commit to a work item so it’s easy to find with your version control tool and work planning tool? If you want to know what specific scenario a piece of code was covering then your well named unit test will tell you that. You do write tests don’t you?
    1
  14.  @joanvallve7647  What facts are you referring to? Can you send a link to published peer reviewed research paper for us please? Agree with your views about scrum. Most places I’ve worked don’t really do scrum in that they do not adopt the engineering practices that are at the core of agile. If you’re not adopting these practices you’re not agile. It’s been ambushed by non technical people and think it’s about management. The original signatories of the agile manifesto are software developers, so that should indicate what’s at the core of the idea. These are the same type of engineers that are frustrated when companies/people use the word ‘scrum’. I’m with them. This video explains it better than I can, https://youtu.be/3cmY-OFuuCw?si=cdHxF0KkeZLUDeAr
    1
  15.  @joanvallve7647  More than 15 years so you got that easy to lookup piece of data wrong. So you use the statement ‘Almost no one’, what is this based on? Some data published somewhere? How long something has been around for and the assumption that almost no one uses it is not proof. You can’t just dismiss something and come up with your own opinion as fact. That’s what some religious people do when arguing against scientific findings like evolution. As I’ve asked before get some evidence to back up your argument, if not it’s just your opinion and nothing more.
    1
  16.  @joanvallve7647  How you get to the statement ‘software industry is stupid’ is beyond me. As for evidence that the practice of TDD is a positive thing, if you watch the video studies are quoted that back this up. There are more studies out there that also produced data that would indicate this, I’ll get the links if you want? In the mean time perhaps you can share your data with us?
    1
  17. These people who don’t like change are in the wrong industry I’d say 😃
    1
  18.  @Rope257  💯%
    1
  19. What the heck has agile got to do with the amount of time in meetings? Just goes to show that most people’s interpretation of agile is way off the mark.
    1
  20.  @eyesopen6110  What don’t you understand? You equate agile with meetings, why?
    1
  21. That sounds like defensive coding? I’d rather not spend time maintaining defensive code. Good unit testing (yes TDD) will ensure that you’re never passing a null. Using the result pattern or null object pattern will mitigate having to check for nulls everywhere which makes life easier. I’d also avoid throwing exceptions too, they’re expensive and are just goto statements with knobs on.
    1
  22. Same company also bricked Linux systems earlier this year (Debian & Rocky). However it feels like they need provide another way of accessing the kernel to make it more robust.
    1
  23.  @NicodemusT  As you say nothing is infallible, but tests give us early feedback that something failed. Should we just release our changes to production and cross our fingers then? AI will be another tool for software developers to use that will speed up development. Will it totally replace developers, in its current state I really can’t see it.
    1