It’s 15 to 20 years old? My first book is Wardley Mapping by Simon Wardley. If every company did continuous delivery, they would be flying. It came out this year and is a really great book if you want a more modern take.
SOFTWARE ARCHITECT SOFTWARE
Their ‘Modern Software Engineering’ book is an excellent follow on from them. Their new book is good as well: ‘Modern Software Development’? A lot of stuff from the book is really consumable. Their bite sizes on YouTube are really good.
SOFTWARE ARCHITECT FULL
It’s a world-class book full of good practice and lessons learned. They have an automated pipeline, but they’re not getting the benefits from a truly continuous delivery environment. We see a lot of companies not striving for continuous delivery. To see what lessons they can take from it and apply it to their own ecosystem and environment. It is still as fresh as it was when it was written.Īnd a lot of teams would do well to actually read it again. And it has been massively influential in how high-performing teams deliver their software today. Continuous DeliveryĬontinuous Delivery by Jez Humble and David Farley So I think we should have a quick chat about them. And then ‘The Software Architect Elevator’, by Gregor Hohpe. It is a weird book, but I think it’s brilliant. I really like ‘Creativity Inc’ by Ed Catmull from Pixar.
‘Team Topologies’ is my second and most brilliant book. I’m not sure that he has a name for it, but it’s free on Medium. My first one is Simon Wardley’s ‘Wardley Mapping’ book.
And in particular, Chapter Nine which is about what they do with their developer experience, self-service portal, etc. The last one, I’ve read it a couple of times, is the ‘Ask Your Developer’ book. So I’ve been delving into ‘Design and Data Intensive Applications’ book, which is really good. The other one I’ve been looking at a lot lately because I’m not really a massive data guy. ‘Extreme Ownership’ by Jocko Wellington is a great book.
SOFTWARE ARCHITECT HOW TO
It’s really about leadership, how to R&D it, and helping yourself to think for collaborative strategic conversation. There’s a lot of good stuff that you can reference.įor the next one, I really like the ‘Extreme Ownership’ book. We’re doing lots of domain-driven design at the minute so the Eric Evans book ‘Domain Driven Design’ has a lot of good common sense. And the ones that Mark listed are in there. I can’t use any of Mark’s now! I value books that I can keep going back to or refer to quite a bit. So the top four are the ‘Continuous Delivery’ book, the ‘Accelerate’ book, ‘Reaching Cloud Velocity’, and ‘Working Backwards’. What are your top four? Top 4 books by Mark, Mike, and Dave And then we can have a quick chat about them. So we figured we’d pick out our top four books and list them out. There is a small number of books that have influenced both ourselves and ‘ The Value Flywheel Effect‘ book as well. Books have influenced us as avid readers and through using social media to find out what’s happening. We were having a chat over the past couple of weeks about engineering books to help you become an awesome software architect.
0 kommentar(er)
