Łukasz Bajsarowicz - CTO at FastWhiteCat S.A. & E-commerce Expert

Tailored for real impact

I help you cut through the complexity
to supercharge your growth.
No bullsh*t, just straight-shooting
solutions that hit the mark.

Łukasz Bajsarowicz
about me

I'm Łukasz, CTO at FastWhiteCat S.A.

E-commerce leader with a hands-on approach. Straight to the point.

Top 50 Magento contributor in 2019. Leader in 2020. Passed the Adobe Commerce certification exams since 2018 and earned the Architect status in 2020.

More than just another tech executive. Deep expertise across Magento, Adobe Commerce, Shopware, and Sylius — backed by hands-on DevOps: Terraform/OpenTofu, CI/CD, infrastructure as code…

I lead e-commerce technology at FastWhiteCat, turning complex challenges into scalable solutions. No sugarcoating, just real results.

11

Years in ecom
Development

523+

Open-source
PRs merged

360+

Pull Requests
reviewed

Łukasz Bajsarowicz
Want to talk e-commerce? Let's connect.
Write a message!
recent blog posts
Article category:
  • Magento / Adobe Commerce
  • Personal
Magento Cloud: Fastly dashboard in NewRelic

Magento Cloud: Fastly dashboard in NewRelic

Monitoring your e-commerce infrastructure plays a key role in improving performance and service availability. While investigating excessive usage of CDN traffic. Learn step-by-step how to set up Fastly dashboard in your NewRelic.

read more →
Want to read more publications? Visit blog
recent open-source contributions

Not articles — code. Shaping the tools I use every day, with a note on what was actually broken.

fix sansecio/magento2-module-shield #43 merged

Set a timeout on the Shield rules fetch  — on GitHub

Magento\Framework\HTTP\Client\Curl sets no default timeout, so a stalled connection to the rules endpoint blocked fetchRules() indefinitely. That call runs from a cron job in a separate process, and Magento’s schedule lifetime only prunes stale rows after the fact — it never kills the hung worker.

perf sansecio/magento2-module-shield #45 merged

Cache the WAF rules in front of the flag lookup  — on GitHub

The plugin injects the WAF eagerly, so every request paid for a point SELECT on the flag table before it could decode the rules — a round trip for a value that only changes when the five-minute cron writes it. Caching in front of that lookup, without reintroducing the cache-only storage the module had deliberately dropped, since cache:flush or a disabled cache type must not leave the WAF ruleless.

Want to see the rest? All contributions
My Projects