NDC Minnesota - The books list from talks I've been to

NDC Minnesota - The books list from talks I've been to

2018, Apr 23    

I like big books...



  1. The Ideal Team Player: How to Recognize and Cultivate The Three Essential Virtues - Patrick M. Lencioni

    From Amazon : In his classic best–selling book, The Five Dysfunctions of a Team, Patrick Lencioni laid out a groundbreaking, new approach for attacking the dangerous group behaviors that destroy teamwork. Here, he turns his focus to the individual member of a team, revealing the three indispensable virtues that make some people better team players than others.

  2. Strength Finder - Tom Rath

    Whereas a lot of books focus of improving upon your weaknesses, this instead helps you determine what your strengths are so that you can build upon and take advantage of them.

  3. Who Needs An Architect - Martin Fowler

  4. Building Architects - Martin Fowler

  5. Release It! Design and Deploy Production-Ready Software - Michael Nygard

    This book I have already read. I was recommended it as one of the first books I should read when I first started as a Software Developer, and I think that was great advice.

    I am planning on revisiting it in coming months as I think that now I have some experience working in teams with different systems and procedures (for testing, deployment etc) I would have an entirely different perspective on the contents.

    It is also a light enjoyable read. Not an incredibly think book with some examples having fantasy references.

  6. Design It!: From Programmer to Software Architect - Michael Keeling

    I haven’t read this, but it is in the same series as the previous and is definitely in my list. I’m not planning a career change any time soon, but I think the concepts in this book are still useful to me currently.

    From Amazon: Design It! is the perfect introduction to software architecture for programmers who are ready to grow their design skills. Lead your team as a software architect, ask the right stakeholders the right questions, explore design options, and help your team implement a system that promotes the right -ilities. Share your design decisions, facilitate collaborative design workshops that are fast, effective, and fun-and develop more awesome software! With dozens of design methods, examples, and practical know-how, Design It! shows you how to become a software architect

  7. The Art of Agile Development - James Shore

    Whether you are used to working in an agile environment and want a new perspective or you are thinking to moving towards more agile practices, this book was recommended.

    From Amazon: This book provides no-nonsense advice on agile planning, development, delivery, and management taken from the authors’ many years of experience with Extreme Programming (XP). You get a gestalt view of the agile development process, including comprehensive guidance for non-technical readers and hands-on technical practices for developers and testers.

  8. Software Architecture in Practice - Len Bass, Paul Clements, Rick Kazman

    This book was recommended for any aspiring software architects, or anyone who wants to learn more techniques for designing, developing, or managing large software systems.

  9. Domain-Driven Design: Tackling Complexity in the Heart of Software - Eric Evans

    This is on my reading list. I have read the lighter Domain-Driven Design Distilled by Vaughn Vernon to learn some of the core concepts, but have been told by a few people that the Eric Evans book is an essential read. It is a bigger book with an appropriately bigger price tag. Apparently it is a book you can revisit many times over though.

  10. Visualise, document and explore your software architecture- Simon Brown

  11. Technical leadership and the balance with agility - Simon Brown

  12. Agile Software Development: Software Through People - Alistair Cockburn

    From Amazon: Written for developers and project managers, Agile Software Development compares software development to a game. Team members play the game knowing that the ultimate goal is to win–always remembering what they have learned along the way, and always keeping in mind that they will never play the same way twice. Players must keep an open mind to different methodologies, and focus on the goal of developing quality software in a short cycle time.

  13. Agile Software Development: The Cooperative Game: The Cooperative Game - Alistair Cockburn

    From Amazon: Alistair Cockburn begins by updating his powerful model of software development as a “cooperative game of invention and communication.” Among the new ideas he introduces: harnessing competition without damaging collaboration; learning lessons from lean manufacturing; and balancing strategies for communication. Cockburn also explains how the cooperative game is played in business and on engineering projects, not just software development.

    and suggested video along with the above two What Makes Agile Work

  14. Responsibility Driven Design - Rebecca Wirfs-Brock

    Again, a short read I plan on finishing over my morning coffee some time soon. From the talk I watched I gather this concentrates on the responsibilities and behaviours of the objects in your domain. How accurate my notes are, I’m not sure! I will update this when I know more.

Overall

The majority of these I will be adding to my own list (I may make edits to this post as I complete them). This reading list was from the total of 3 talks as I forgot to take my notepad to some of the ones I attended foolishly.

I would love to hear some of the book recommendations some of you have got from attending talks at meetups and conferences, and how appropriate they have been for your needs.



step 1