4Developers 2019 Warszawa
2019-04-08
Warsaw, Poland
[4Developers 2015, 4Developers 2017, 4Developers 2019, 4Developers 2019 Warszawa, 4Developers 2020, 4Developers 2021, 4Developers 2022 Online]
| title | author | length |
|---|---|---|
| Structures of Thinking: Mental Models, Levels of Reasoning (...) | Artur Król | 40m |
Covers how the human brain’s hardware and cognitive limits (like working memory) shape everyday thinking and communication. Explains why people use jargon… | ||
| The Return of the Native Principles | Bartłomiej Słota, Paweł Szymczyk | 47m |
Discussion of core programming principles—abstraction, encapsulation, SOLID, and GRASP—and how they map to project and system architecture and team… | ||
| Event Storming - how to shorten the distance between IT and Business | Sławek Sobótka | 55m |
Covers Event Storming as a workshop technique to bridge business and IT: how architects and analysts run sessions to extract domain knowledge and derive… | ||
| How does the architect know? | Łukasz Szydło | 46m |
The talk examines why many programmers distrust software architects and whether architecture is necessary versus self-organizing teams. It presents a… | ||
| Refactoring Live Session Toward Tactical Domain-Driven Design | Michał Michaluk | 47m |
A live-coding refactoring session demonstrating how to migrate a legacy, untested, and poorly understood codebase into an object-oriented, contextual Domain… | ||
| EventStorming Lessons Learned - tens of thousands of post-its later | Mariusz Gil | 40m |
Covers practical lessons from running many EventStorming workshops since 2015, including using Post‑it based modeling with EventStorming for Domain‑Driven… | ||
| Distributed journey | Piotr Gankiewicz | 44m |
Covers building distributed systems and the practical trade-offs of tools and patterns for problems like communication, messaging, authentication, routing… | ||
| Architectural Patterns and Approaches Supporting Refactoring(...) | Szymon Szylhabel | 46m |
Explains why starting new projects as microservices is usually a bad idea and argues for beginning with a well-structured monolith instead. Describes… | ||
| nothing matches | ||