Modern Software Engineering • Dave Farley & Steve Smith • GOTO 2022

This interview was recorded for the GOTO Book Club. #GOTOcon #GOTObookclub
gotopia.tech/bookclub
Read the full transcription of the interview here:
gotopia.tech/bookclub/episode...
Dave Farley - Author of "Modern Software Engineering",
Continuous Delivery & DevOps Pioneer
Steve Smith - Author of "Measuring Continuous Delivery",
Principal Consultant at Equal Experts
Find plenty more from Dave on his Continuous Delivery KZbin channel: / @continuousdelivery
DESCRIPTION
What should the modern software engineer know in order to be the best at their job? Dave Farley and Steve Smith explore the books that can help engineers succeed and why iteration and experiments are crucial.
The interview is based on Dave's book "Modern Software Engineering": amzn.to/3GI468M
TIMECODES
00:00 Intro
01:45 Software engineering books that shook our foundation
06:36 Modern software engineering in practice
09:52 Working iteratively
18:33 The experimental software engineer
29:09 Managing complexity in the cloud age
40:16 How to apply the separation of concerns in a team
46:28 Rolling the wheel of time
53:15 What’s next after Modern Software Engineering?
01:03:52 Outro
RECOMMENDED BOOKS
David Farley • Modern Software Engineering • amzn.to/3GI468M
Dave Farley & Jez Humble • Continuous Delivery • amzn.to/3ocIHwd
Steve Smith • Measuring Continuous Delivery • amzn.to/3MEAJbe
Eric Evans • Domain-Driven Design • amzn.to/3tnGhwm
Kent Beck • Extreme Programming Explained • amzn.to/34OVMH6
Michael Feathers • Working Effectively with Legacy Code • amzn.to/37suHdy
Alistair Cockburn • Agile Software Development • amzn.to/3u0zNVX
Mary & Tom Poppendieck • Implementing Lean Software Development • amzn.to/3CQwC7t
Fred Brooks Jr. • The Mythical Man-Month • amzn.to/31NJc5C
Simon Brown • Software Architecture for Developers Vol. 2 • leanpub.com/visualising-softw...
Woods, Erder & Pureur • Continuous Architecture in Practice • amzn.to/2QWAmkl
George Fairbanks • Just Enough Software Architecture • amzn.to/3uZzVo0
/ gotocon
/ goto-
/ gotoconferences
#SoftwareEngineering #DaveFarley #SteveSmith #Programming #Harness #ContinuousDelivery #ModernSoftwareEngineering #SoftwareArchitecture #DevOps #WorkingIteratively #DevOpsTutorial
SUPPORTER
Harness is the only end-to-end platform for complete software delivery. It provides a simple, safe and secure way for engineering and DevOps teams to release applications into production. Try Harness for free! app.harness.io/auth/#/signup/...
Looking for a unique learning experience?
Attend the next GOTO conference near you! Get your ticket at gotopia.tech
SUBSCRIBE TO OUR CHANNEL - new videos posted almost daily.
kzbin.info...

[@GOTO-]

Links to referenced books can be found in the video description. Link to Fred Brooks' original article "No Silver Bullet Essence and Accidents of Software Engineering": ieeexplore.ieee.org/document/1663532 Wikipedia: en.wikipedia.org/wiki/No_Silver_Bullet

[@Mikenight120]

Amazing conversation between professionals. Loved how open they spoke. Great video🦾🦾

[@IbrahimKhan-bi5yk]

J .., kgtgx u LgSa byra b big a CD

[@seguntayo155]

Systems Engineering is got to be the most difficult way to solve problems but the most effective. This is because "Systems" are of the highest order when it comes to the creation of things, which is just a basic fundamental in defining "Engineering". So, the thinking should be toward the lowest order of creating things which is the basic unit of a thing, be it "atom" or "cell" or anything at the very foundational level. Thank You. My understanding of what was discussed towards solving problems.

[@xilconic]

Loved the discussion and banter between experienced software engineers passionate about the subject. Thank you.

[@LennartStoop]

Great talk, personally i find reducing complexity always works in software development, no matter the context

[@michaelmboya5085]

This was good to watch

[@jackieli1724]

Good Video

[@PaulSebastianM]

Such a sincere opening :).

[@seguntayo155]

Tools do not define success, they only progress our reaching a solution to a problem. So, it is about the understanding of the problem and the way we use the tools to solve the problem. We are not trying to solve problems using the tools better because new, better tools become crafted later on, which helps us to progress faster and better in our solution to the problem.

[@conw_y]

13:30 Iteration isn't enough though... you might get stuck in a local maxima. You need broader knowledge and synthesis to know how far back down a mountain you will need to descent, i.e., how fundamental your error is.

[@ManojGanapathi42]

If I had to summarize, Modern Software Engineering presents what I call as the "Dual Challenge": Embracing New (& often complex) architectures leveraging Digital technology While keeping Release cycles short

[@edgeeffect]

I mostly agree with Dave on the subject of technology specific books... but there's always a couple of exceptions to the rule.... I've always thought Douglas Crockford's "the Good Parts" was vital reading if you're a JS developer or not just because of the ideas it smuggles across in it's technology specific text.

[@ZapOKill]

there is no 10x ! ... but a lot 0.1x