Page 30 - Maxim Mironjuk

only and except were the standard way to run jobs conditionally in GitLab CI for years, but the rules keyword has superseded both for a long time and enables condition logic that only/except simply cannot express. This article shows why the migration pays off and how it succeeds step by step in existing pipelines.

Anyone lifting a grown PHP project onto PHPUnit 10 or 11 runs into a flood of deprecation notices, changed assertion signatures, and removed interfaces. This article shows a structured path through the migration, without endangering the running test suite and without having to touch every test class at once.

A test that sometimes passes and sometimes fails is worse than no test at all. It erodes trust in the entire test suite, forces manual re-runs and hides real regressions behind noise. Flaky tests arise from specific root causes, and every single one of them can be fixed for good.

A design team usually hands over exactly one hex value for the brand color, while Tailwind expects a complete scale from 50 to 950 for backgrounds, borders, text and hover states. Anyone who tries to click together those eleven steps by hand in a graphics tool rarely gets a consistent result, because lightness and saturation are hard to space evenly without a fixed color space. An OKLCH-based interpolation automates that process and produces scales that feel just as even as Tailwind's own built-in palettes.

Testing discount and tax calculations with only a handful of hand-picked example values checks nothing but the cases you happened to think of while writing them. Property-based testing lets a library generate hundreds of random inputs, verify a general property such as never negative, automatically surface edge cases, and shrink every failure down to the smallest possible counterexample.

The Notifications API only displays what already lives in the browser. To actually reach users after the tab has long been closed, you need the Web Push API: VAPID identity, a push subscription, and a server that delivers through the browser's push service.

Giving every application and developer the same database account with full rights automatically turns any future security gap into total damage. Granular database user privileges, built from GRANT statements, role hierarchies and the principle of least privilege, limit the damage of a single compromised account to exactly what that account genuinely needs.

DI, Repository, ViewModel, Plugin, Observer, Factory, Proxy, MVC, Strategy, Iterator, Active Record, Singleton, Registry and more: all 13+ architectural patterns in Magento 2 explained, with code examples and the knowledge of when which pattern is the right choice.

A clean Magento 2 module is not just registration.php and module.xml. Production ready code also needs configuration, ACL, an admin menu item, layout XML, a ViewModel and clear dependency injection.

Google core updates are broad reassessments of relevance and content quality, not penalties for individual technical mistakes. Chasing individual ranking factors after a traffic drop wastes valuable time and resources. This article shows how to diagnose a genuine core update impact, correctly read Search Console performance data, and build stable long term rankings through a holistic content quality review.