For those in a hurry, there is a link to the presentation:
There is a certain art in the architecture of software, a subtle elegance that is revealed in the structure and organization of code. It's an art that not everyone can master, especially because not everyone knows it. But those who do are capable of creating masterpieces. Masterpieces in terms of flexibility and extensibility (open-closed principle), masterpieces in terms of maintainability, and masterpieces in terms of readability (screaming architecture). And as befits true masterpieces, they are destined to stay rather than be struck down by a random sow in the village of rewriting.
Clean Architecture is such a concept that allows one to create such a masterpiece or to transform an application that is slightly out of date into one. A concept introduced by Robert C. Martin, also known as Uncle Bob. In my opinion he was just pouring old wine into new bottles, because the concept of domain-centric architectures, be it onion architecture or hexagonal architecture, existed before that. Still, Uncle Bob deserves credit for his outstanding ability to reach the masses, while the cries of others closer to ivory often go unheeded, and it takes years for their grandiose ideas to catch on. Just think of REST, many years passed from the publication of Roy Fielding's dissertation in 2001 to its widespread use and acceptance.
But back to the topic: A while ago I was challenged to give a talk on this topic. Full of joy (because it's one of my favorite topics) I accepted the challenge and created a presentation that conveyed the basics of clean architecture in an understandable and accessible way. The presentation was a success that encouraged me to make my presentation available to you completely ad-free and free of charge.
One thing should be said: clean architecture is not a panacea and is not suitable for every project or every situation. Because during my years as a software architect, I've learned that it's the business value that counts, not the architect's belly-painted ego. If an outdated application that has lost its sex appeal and is based on the classic 3-tier model is still filling the coffers of the customer and each new release is not disproportionately more expensive than the previous one, then as a consultant I would advise against switching to clean architecture just for reasons of coolness. But that's just a side note.
I created my presentation with Beautiful.AI. The name may suggest that a bot has done everything for me here. Not even close. I am someone who creates all graphics myself (see: https://www.wackyworld.de/digital-art) and I love slides that contain more images than words. It's probably called Zen design. So far I haven't found a tool that pours my picture thinking into slides faster than Beautiful.AI. I even used it recently for a self-presentation for a project initiation meeting. Lo and behold, I got the contract. But don't worry, I don't get any commission if you use the tool. As a freelancer, however, I am always pressed for time. I can't bill the client for wasted minutes, so I'm concerned about efficiency. And this tool has greatly increased my efficiency in creating presentations.
There will be an update soon in which I will also add PDF files for download.
Finally, I would like to say a word about my old video on this topic: https://www.wackyworld.de/post/clean-architecture-the-big-picture
I wouldn't do it the same way today. It was too cumbersome and I focused too much on the technical details, while the content fell short. But a growth mindset, which I self-confidently ascribe to myself, is also characterized by the fact that you learn from your mistakes and don't make them more than once.