Page 172 - Maxim Mironjuk

"Segmentation fault (core dumped)" in the log marks the end of the investigation for many teams instead of the beginning. Yet a correctly enabled core dump combined with gdb and coredumpctl almost always yields a complete backtrace down to the exact line of code. This guide shows how to configure core dumps correctly on Linux, read backtraces, and systematically narrow down typical causes such as faulty PHP extensions.

mironsoft.de › Blog › Design Patterns

Magento 2 · Design Patterns

Service Locator &
ObjectManager in Magento 2

The ObjectManager is the Service Locator pattern in Magento 2, and at the same time the platform's best known anti-pattern. This article explains why using it directly in production code is forbidden, which exceptions are legitimate, and what correct Dependency Injection looks like.

13 min read PHP 8.4 Magento 2.4.8

Table of Contents

1. What is the Service Locator pattern?
2. The role of the ObjectManager in Magento 2
3. Why ObjectManager::getInstance() is an anti-pattern
4. SOLID principles and how ObjectManager violates them
5. Legitimate exceptions: when the ObjectManager is allowed
6. The right way: Constructor Injection in PHP 8.4
7. Factories instead of ObjectManager::create()
8. Mocking and refactoring the ObjectManager in unit tests
9. Recognizing and fixing typical code smells
10. Summary
11. FAQ

What is the Service Locator pattern?

The Service Locator pattern is a design pattern for resolving dependencies

.env files look like plain text files at first glance, but PhpStorm treats them as a dedicated file type with syntax highlighting, inspections, and auto-completion. Used correctly, this prevents exactly the errors that would otherwise only surface at runtime inside the container.

Incremental Static Regeneration combines the delivery speed of statically generated pages with the freshness of server-rendered content, by regenerating individual pages in the background once a defined cache window expires, without needing a full rebuild of the project. This article shows how to configure ISR in Nuxt through routeRules, where the difference to SWR lies, and what a practical use case with product pages looks like.

Date.now() delivers milliseconds with a precision that is not sufficient for serious performance measurement, and falls into the trap of system clock synchronization. The JavaScript Performance API provides sub-millisecond timestamps, structured marks and measures, a non-blocking observer mechanism, and direct access to Web Vitals without an external library.

Instagram Reels and YouTube Shorts look interchangeable at first glance as variants of the same short video format, but they work on fundamentally different discoverability mechanics. While YouTube Shorts benefit directly from the text based search index and tight Google integration, the visibility of Instagram Reels depends almost entirely on the internal recommendation algorithm. This article compares both formats on a solid technical basis, highlights typical cross posting pitfalls, and offers a practical decision guide for allocating resources within a team.

docker stack deploy turns a familiar compose file into a complete, highly available Swarm stack, including networks, volumes, secrets and configs in a single rollout. Knowing the differences between local compose and stack deployment helps you avoid the most common pitfalls when moving from development to production.

Not every team uses GitLab's own Kubernetes integration. Often a plain kubectl call directly from the pipeline is enough, as long as the kubeconfig and access rights are configured cleanly and safely. This article walks through the full path from the kubeconfig variable to a verified rollout.

For years, animating an element as it appeared from display:none required JavaScript. CSS @starting-style solves this problem natively, enabling elegant transitions for popovers, dialogs and dynamically inserted content without a single line of JavaScript.

Next.js middleware runs before a route is even rendered, deciding on redirects, rewrites, and headers before Server Components or Client Components become active. Once you understand matcher rules, auth checks, and the limits of the edge runtime, you can build routing logic that stays fast and still behaves robustly.