Comments by "Lee Rothman" (@leesoftwareengineer) on "The CrowdStrike Crisis Proves The Software Industry MUST CHANGE" video.

Sorry but I disagree, developers are responsible for the quality of their work not management. I still see teams wanting permission to do things the write way, I’ve no idea why. Just do it, if a product owner or manager asks you to write a dirty hack say ‘no’. I know that some people do put a lot of pressure on developers to always choose the crap hack option, but they are not responsible for the quality of the code, developers are.
4
@Marck1122 Don’t write stupid automated tests then. Write meaningful automated tests that covers all the logic.
3
Well if you mean most companies don’t implement best engineering practices whilst they ‘think’ they’re agile I agree. However that’s not a problem with an agile framework just a bad implementation of one. Sprints don’t lead to bad design, lack of good development practices does.
3
@Marck1122 Well I can’t think of logic you can’t cover in an automated test. Maybe I’ve just been lucky in the time I’ve adopted practices like TDD and CD? Can you give an example and hopefully there might be a way to automate? The only code that I can think of is the look and UX of the client-side, the functionality of the client-side is though.
2
@rui1863 Agreed. I’ve heard it described as ‘the language of violence’. ‘You must complete all the stories that you committed to during sprint planning’, ‘you have to increase your velocity’, ‘if you don’t deliver this functionality then you’ve failed the sprint’ etc etc. It’s often used as a shitty stick to beat people with. I still think that the main problem is a bad understanding of what agile is. I’ve posted on here before about Martin Fowler wrote a blog years ago and labelled it as ‘flaccid scrum’. Some think that because you have a sprint board, use story points and have a standup every morning then they’re agile. If you’re not doing the whole engineering excellence thing then you ain’t agile. I much prefer kanban to scrum personally. No planning an iteration worth of work, just the highest priority item, no sprint goal. As for the use of the word framework, I’m just quoting the scrum alliance definition. ‘As an agile framework, scrum provides………’
2
Testing shouldn’t be a separate process after the code is written, but whilst the code is being written. The state of devops report shows that lots of small releases results in fewer issues than a releasing lots of changes in bulk.
2
Maintaining automated tests is a lot cheaper than fixing bugs and spending half your time debugging. Teams that follow XP practices spend more time writing new features because they not fixing bugs.
2
@ndewet Well there’s certainly been loss of life due to bugs. NHS systems didn’t sent out letters to patients to book follow up scans for breast cancer. You can guess the outcome for some of those patients. Toyota had break failures in 2009 which resulted in deaths, caused by a software issue. Several suicides have been linked to the horizons scandal. Self driving car caused the death of a pedestrian 2018. I’ll stop there. 😢
1