User Profile

cosocial.ca/@evan

mastodon.energy/@Sustainable2050/113681807165629296

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.

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.

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.

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.

hachyderm.io/@nick_tune/112502664363675915