Educator and researcher in software engineering at Delft University of Technology. Although I love fiction, I use this Bookwyrm account mostly to manage professional books on software architecture, testing, technical leadership, and digitalization.
This link opens in a pop-up window
This landmark 1971 classic is reprinted with a new preface, chapter-by-chapter commentary, and straight-from-the-heart observations on topics that affect the β¦
ActivityPub is the new standard for connecting social networks together on the social web. This β¦
In previous books, Holocaust historian Timothy Snyder dissected the events and values that enabled the β¦
Effective software teams are essential for any organization to deliver value continuously and sustainably. But β¦
Book with a simple, useful and actionable message: design software architectures and team interactions together, since they are similar forces. And a nice and simple model of four team types.
Implementing Domain-Driven Design presents a top-down approach to understanding domain-driven design (DDD) in a way β¦
I'm sure there will be readers who love this book, but I'm not one of them. The language is too imprecise, the text is wordy, and I fail to grasp the cowboy jokes. A huge contrast with the immensely compelling writing style of Eric Evan's original book introducing Domain-Driven Design.
Methods for managing complex software construction following the practices, principles and patterns of Domain-Driven Design β¦
This book is a useful companion to the Eric Evan's original "blue book" on Domain-Driven Design. Millet and Tune flip the order of Evan's book, discussing strategic patterns (bounded context, context maps) before the tactical ones (entities, aggregates, repositories ...). Particularly valuable are the additions of DDD-thinking emerged after the publication of the blue book, like events, event storming, and event sourcing.
The book is full of examples, all in C#, also relying on C# libraries. Nevertheless, the examples are also sufficiently accessible for developers using other languages.
In Patterns for API Design: Simplifying Integration with Loosely Coupled Message Exchanges, five expert architects β¦
Well-organized book with series of useful practices for RESTful API design. We use it as one of the books in the software architecture graduate course at TU Delft.
Nice overview of UML. We use the book at TU Delft in our undergrad software engineering course as a reference. In the lectures we provide a high level overview. In various exercises students then need to actually create diagrams, using this book to understand the details of the various diagram types. Students use plantuml to create the diagrams -- which also has extensive documentation that combines well with this book.
System architecture is the study of early decision making in complex systems. This text teaches how to capture experience and β¦
Good practices, collaboration tools, and effective techniques for incorporating your key stakeholders into the software β¦
"Whether pondering black holes or predicting discoveries at CERN, physicists believe the best theories are beautiful, natural, and elegant, and β¦
Get more out of your legacy systems, more performance, functionality, reliability, and manageability.Is your code β¦
Excellent collection of techniques that will enable you to develop test cases for code that you thought was hard to test.
Very code-centric with a focus on object-orientation. Since the bookβs publication mocking frameworks (e.g. Mockito) have advanced considerably, so some of the ideas are now even easier to use.
The problem of legacy systems is of course bigger than OO code (databases, COBOL). But for cleaning up and testing OO code, this is a great resource.
Classic text on the human side of software engineering, containing essays on the management of software teams, projections about how β¦
