Books

SOLID is an acronym which stands for SRP, OCP, LSP, ISP and DIP. These five acronyms in their turn stand for:Single Responsibility PrincipleOpen/Closed PrincipleLiskov Substitution PrincipleInterface Segregation PrincipleDependency Inversion Principle

Want to write The Next Big Multiplayer Online Game? This series will help you to learn the ropes. Vol.I covers topics such as GDD and Communications.

In an era where software complexity threatens to overwhelm even the most skilled developers, this book emerges as a beacon of clarity. This practitioner's guide provides a battle-tested toolkit for conquering the challenges of modern software development. Dive into the world of Hexagonal Architecture, where flexibility reigns supreme and change is embraced, not feared. Learn how to craft systems that stand the test of time, resistant to the whims of changing technologies and evolving requirements. From the trenches of real-world projects, discover strategies that transform tangled codebases into modular marvels. Unravel the mysteries of effective decoupling, harness the power of dependency inversion, and master the art of building truly adaptable software. Whether you're grappling with legacy systems or architecting the next big thing, this guide equips you with the knowledge and techniques to triumph. Say goodbye to rigid architectures and hello to systems that bend without breaking.

What is a good software architecture? Why should we bother structuring the code and spending time testing it? If you like spending hours debugging your programs or staying late at the office to recover from a buggy deploy in production this book is definitely NOT for you!

? Crack the Code of Complex Business Domains! Struggling to align software with ever-changing business needs? "Domain-Driven Design Essentials" gives you the battle-tested patterns to: ? Speak the same language as stakeholders (no more misaligned requirements!)? Slash maintenance costs with Clean Architecture + DDD? Tame legacy systems using strategic decomposition? Spot hidden traps (like the Anemic Domain Model antipattern) "Finally – DDD explained for working engineers, not academics." Professional Programmer Series (https://www.professional-programmer.com)

In unethical software, not every line of code is written with good intentions. Unethical Software Engineering: Dark Patterns exposes how to manipulate users, drive profits, and evade accountability. From covert surveillance, monetization at all costs, digital fraud, ranking manipulation, all the way to unethical artificial intelligence practices, this scary book unveils how these "dark patterns" exploit human beings, erode trust, and disrupt digital ethics.Whether you're a developer, an architect, a tech enthusiast, or simply a concerned user, this book will change how you think about your daily apps — and inspire you to demand better. By helping you to draw the line between what is acceptable and what is questionable, Unethical Software Engineering: Dark Patterns shines a light on the digital dark side of software engineering where profits are prioritized over people.

Go beyond pixel-deep diagrams - generate documentation sites, make them executable, map to your problem domain, federate into a web of diagrams

Die Domain-driven Design Referenz gibt einen Überblick über die grundlegenden Pattern für Domain-driven Design. Domain-driven Design ist ein Ansatz für die Architektur und das Design von Software-Projekten, das sich konsequent nach den fachlichen Anforderungen richtet..Die Referenz wurde vom Erfinder von DDD, Eric Evans, in Englischverfasst.

A primordial Forth, and some related philosophy.

The Scaling Playbook From WordPress to 1 million orders. One company's 5-year journey through every scaling decision, mistake, and hard-won principle. No code. No fluff. Just architecture thinking.

The easiest (and shortest) entry point to Event Storming and Domain-Driven Design you will find for free. I designed this book to be as close to a workshop experience as possible, and I did my best to make it so. Instead of focusing solely on abstract concepts, you will follow a real-world case study throughout the chapters.

The book describes the evolution of typical web project architecture, which grows step by step by making changes in architecture, like moving some parts to their own layers, improving error handling, and maybe rethinking how data is stored.

Peer-to-peer (P2P) networks are fascinating! P2P networks can scale to thousands, millions or even billions of individual peers collaborating without a central, coordinating entity. These peers can be run by individuals or organizations - each contributing resources towards the total capacity of the network. This book explores how!

One of the most misunderstood XP techniques might be Refactoring. Many understand it in the meaning of re-write which is definitely not what it was meant to be. See how refractoring an example taken from a real world project both consits of very small sometimes even tiny changes and still introduces major archiectural reconstructions.

Dieser praktischer Leitfaden zeigt Ihnen, wie langjährig gewachsene Softwaresysteme effektiv analysiert und bewertet werden können.