Organizing code by architectural concept rather than by feature obscures its true purpose and makes it difficult to understand.
Design patterns originated as named solutions to common problems, but true design begins where these predictable patterns end.
Inspired by Donald Knuth's "Literate Programming," software should be viewed as a constrained form of communication between programmers.
The book "Clean Code" has become a historical artifact that promotes dogmatic adherence to syntactic hygiene over meaningful architectural discussions.
The physical layout of code, including whitespace and grouping, is a powerful tool for communicating intent and improving readability.
The complexity of an application should never exceed the inherent complexity of the problem it is designed to solve.
Merging dozens of separate projects into a single logical application dramatically reduced build times and cognitive overhead for the team.
Complexity is the accumulation of small issues that make a system hard to understand and modify, leading to change amplification and high cognitive load.
The best abstractions, like `file open`, are deep modules that hide significant complexity behind a very narrow and simple interface.
Effective software design is an exercise in making intentional trade-offs, as any design principle becomes absurd when taken to its extreme.
A curated list of books provides a modern canon for thinking about software design, complexity, and maintainability.
Sensory-Minds GmbH
Offenbach am Main, Germany
26:22David Tielke
24:38Carola Lilienthal
30:40Olivier Gaudin
43:13Carola Lilienthal
25:40Julian Lang
28:40Reka Horvath
42:02Simon Lasselsberger
28:13Erick Wendel
Jobs that call for the skills explored in this talk.
Coreweave, Inc.
