| Random Link ¯\_(ツ)_/¯ | ||
| Sep 28, 2021 | » | Object-Oriented Design Patterns
(9 items)
Intro to Design Patterns; OOP Structural Patterns: Decorator; OOP Structural Patterns: Facade; State Machine; Strategy; OOP Creation Patterns: Builder; OOP Creation Patterns: Singleton; OOP Creation Patterns: Factory Method; Observer; |
| Aug 1, 1997 | » | [ToDo] Design Patterns: Elements of Reusable Object-Oriented Software
1 min; updated Sep 16, 2026
Design Pattern Catalog
Design Patterns: Elements of Reusable Object-Oriented Software.
Erich Gamma; Richard Helm; Ralph Johnson; John Vlissides.
|
| Sep 28, 2021 | » | Observer
8 min; updated Sep 16, 2026
Rant: some of willchan’s thoughts on WeakPtr, for those who care to read criticizes the observer pattern for murking dependency chains. Investigate more in this regard. IntentA one-to-many dependency between object so that when one object (subject) changes, all its dependents (observers) are notified and update automatically. ... |
| Mar 30, 2023 | » | Intro to Design Patterns
3 min; updated Sep 16, 2026
What Are Design Patterns?Arriving at designs that are specific to the problem at hand but general enough to address future problems and requirements is hard. New designers tend to be overwhelmed by the options available. Expert designers do not solve every problem from first principles; they reuse design patterns. I’ve also encountered the “you aren’t gonna need it” (YAGNI) school of thought that aims to minimize writing code that anticipates too far into the future, as such guesses usually don’t pan out. Design patterns seem like they exist somewhere between designing for now, and designing for a possible future. A design pattern solves a specific problem being encountered now. And even within a design pattern, one could still adhere to YAGNI, and add pieces when needed. When it does come to the point where the design needs more features, at least the design pattern provides a mental framework that is consistent with the initial design of the system. ... |
notes that , the primary source, glosses over nitty-gritties. e.g. the “message queue” server. Maybe reading through these will provide a larger perspective to design decisions made in Chromium regarding observers.