Learning from Big Public Software Failures | Kevlin Henney In The Engineering Room Ep. 6

[@eduardo_bray]

Hi Dave, I've been following your channel since the beginning and for me has been one of the most useful and meaning software development content on YT. I really want to thank you for your work and for "open the mind" of those with less experience like me. Implementing my first pipeline has been a though journey but, as you pointed up, is a lifechanger. Thank you so much for sharing your knowledge and work! Grettings from the south of the world.

[@MatthewChaplain]

6:07 - Archaeology of Failure is a fantastic book title, and I would buy it.

[@kayakMike1000]

OMG... I love Kevlin Henney, he's funny and smart.

[@sadranezam3367]

this convo has hit a perfect balance between being philosophical and practical , and i love it!

[@NickDixon]

This is a fascinating.thing to watch. The Engineering Room is always interesting, whoever the guest is, but I swear you and Kevlin could have a YT channel that's just the two of you chatting like this.

[@pacifico4999]

I'll do a presentation in my company and Kevlin is one of my inspirations. Wish me luck 🤓

[@tlooy24]

Brilliant and entertaining video. Thanks Dave andKevlin!

[@mrpocock]

The deeper issue with Java-style exceptions is that they reinforce to the API designer and consumer that deviations from the golden path are exceptional. In reality, they are in any sufficiently large system the more frequent execution path. Not only are there more failure states than success states, but if you compose enough of these together, then in any given execution it is more likely to hit at least one failure state than zero. The FP approach where you explicitly pass the failures back as part of your function return value gets rid of this idea of error states as exceptional. It forces you to handle and recover from these error states as a core part of expressing your golden path, all without the rather extreme tool of nuking the stack.

[@NachtmahrNebenan]

When I discovered Kevlin on KZbin I searched for all his talks on different topics. He very much influenced my ideas about anything in software development. And my IDE code formatting settings are named 'Kevlin' 😄 Now I'm also eager in getting all new Dave's short talks about continuous integration - Thanx, Dave! 👋

[@ContinuousDelivery]

Great! I hope you find the videos useful.

[@drivetrainerYT]

What a guest! Thanks a lot

[@psyaviah]

Excellent episode!

[@aaronlinton-chambers]

I did a great group workshop with Kevlin which inspired me to explore unit testing. He was able to break down the fundamental concepts about what unit testing in a enjoyable way.

[@bigstones84]

What's the connection between coupling and build time? Incremental compilers?

[@Trezker]

Software development is not a straight wide highway where you can just add horsepower to go faster. It's a hike through mountains where you may find animal paths if you're lucky and you may be at altitudes where oxygen is scarce. There may be rock slides, snow storms, panthers and bears.

[@logiciananimal]

On "programming is not doing math", crypto shows this clearly in my view - if software were math, how would sidechannels work?

[@choudhuryprabir]

Hi Dave, i have been following all your talks and really admire you. I am a part of Innovation board in our company and i don't know if I am allowed to ask - what's the procedure to host you in our company for a talk on continuous delivery.

[@ContinuousDelivery]

Hi Prabir. Thanks for reaching out. You can e-mail me [e-mail]

[@brownhorsesoftware3605]

Excellent video! Make haste with deliberation.

[@brownhorsesoftware3605]

You might like to know the rest of this quote. It is "A good rider is never in a hurry. Make haste with deliberation. " The source is my riding mentor and the advice is on how to jump a stadium course. It's a timed event but if you go too fast the horse will jump flat and knock down rails and you won't make tight turns. So you walk the course, plan your route, and then try to convince your horse to execute the plan. Not so different from writing software.

[@YvesHanoulle]

can you link the documents that Kevlin is talking about?

[@PeerReynders]

Look up "NATO Software Engineering Conference. Garmisch, Germany, 7th to 11th October 1968" Kevlin Henney's talk is Beauty of Code 2018 "1968" or Build Stuff Conference 2018. Martin Thompson also references that document at his GOTO Amsterdam 2017 "Engineering You" talk. If you're interested in Christopher Alexander material look up (for example) "A City Is Not a Tree" for a sample.

[@YvesHanoulle]

@@PeerReynders I have the document on my computer. I was asking to have it linked on the video, because I think many people will like to look at it.

[@RudhinMenon]

Learning from other's failure, my favourite, not trying to be sadist here

[@Rodhern]

For the record: Squared paper is great!

[@cmdv42]

💯💯💯

[@judas1337]

For me there’s too much moving stuff on the screen. I’m trying to take note of body language but it’s drowned out by the rest.

[@ContinuousDelivery]

Thanks for the feedback about the background. We'll tone it down! for future episodes.

[@zerettino]

Great content as usual, but the animated background and frames are really annoying.

[@ContinuousDelivery]

Glad you enjoyed it, and thanks for the feedback about the background. We'll tone it down! for future episodes.

[@BryonLape]

Though Google will give you other people with (somewhat) similar names, there is only one of me.

[@pendax]

The background is a bit annoying.

[@ContinuousDelivery]

Yes, we've calmed things down for the next episode! Please watch my chat with Randy Shoup tomorrow 😁

[@johnridout6540]

Fantastic talk. Please, please, please, don't use those animations again.

[@ContinuousDelivery]

Glad you enjoyed it, and thanks for the feedback. We'll tone it down! for future episodes.

[@CodeShudder]

It's always a pleasure listning to {podcast.guestName}