Design Patterns: Guides and Practical Know-how | Page 13 | mironsoft Blog
Design Patterns
-
Jun 1, 2025
Event delegation uses the DOM's native bubbling behavior to serve every child element with a single listener on the container, instead of registering one listener per list item inside an x-for loop. This article shows how the pattern is implemented in Alpine.js components and where its limits lie.
-
May 31, 2025
Numeric grid lines such as line 3 or line minus 2 are unambiguous for the browser, but hard for humans to remember. Named grid lines and grid-template-areas translate the same grid into meaningful labels and ASCII diagrams that document, right inside the code, what happens on screen.
-
May 31, 2025
The built in Error class from JavaScript is rarely enough for a growing codebase: it carries no error codes, no structured metadata, and no clean serialization. A well thought out error class hierarchy solves these problems with a shared base class, consistent instanceof checks, and cause chaining for connected failure causes.
-
May 29, 2025
A modular monolith splits a Symfony application into clearly bounded modules, each shipped as its own bundle with its own data layer and defined interface. That keeps a growing project maintainable without immediately taking on the operational complexity of microservices. This article shows the concrete directory layout, the communication between modules and how Deptrac enforces architectural boundaries automatically.
-
May 22, 2025
The page object pattern is meant to decouple tests from selectors and DOM structure, but in practice it often balloons into classes with hidden business logic and deep inheritance chains. This article shows what the pattern actually solves, which overengineering traps are common, what a minimal page object looks like, and when a test is better off without the pattern entirely.
-
May 21, 2025
Whether it is an order history, an audit log, or a project's activity feed, chronologically ordered events are one of the most common recurring UI patterns in web applications. Visually there is more to them than it first appears, from the vertical connecting line between events, through icon badges per event type, to handling description text of wildly varying length without breaking the grid. This article shows how to structure a timeline component cleanly with plain Tailwind CSS and where a compact activity list diverges from a detailed timeline view.
-
-
May 13, 2025
As soon as a class uses two traits with same-named methods, PHP reports a fatal error unless the conflict is resolved explicitly. insteadof decides the winner, as assigns alias names and changes visibility. This article shows both operators in detail and where trait conflicts typically arise in real projects.
-
May 9, 2025
Once an application consists of several containers, the chosen communication pattern determines the stability, coupling and fault tolerance of the entire system. From direct name resolution through sidecar and ambassador patterns to asynchronous message queues, this article shows which pattern fits which requirement.
-
May 9, 2025
Polymorphic components let the caller decide which HTML element actually gets rendered, without the component itself needing a separate variant for it. With the as prop and TypeScript's ElementType, this flexibility stays fully type safe, including correctly inherited props and working ref forwarding.