🔥The 9th Round of Easy Loan, Earn $40 Reward is in progress❗️ ⏰ Promotion Period: January 15th - Feburary 15th, 2025 👉 Register now and check more details at gate.io/campaigns/358

No stress, it’s just a conference room. The room :) Devoxx Poland 🇵🇱 11 - 13 June 2025

Very good talk about the dark side of async code reviews by Dragan Stepanović - see you on BlueSky This stuff shouldn’t be controversial Devoxx Poland 🇵🇱 11 - 13 June 2025

Passing TypeScript errors through ChatGPT produces Elm-like compiler errors for humans.

A whirlwind tour around feature toggles from Devoxx Poland 🇵🇱 11 - 13 June 2025 2023. Probably my most rehearsed and polished talk ever :) youtube.com/watch?v=kIAOiz…

Oh my - we’re getting a little famous! 😀 Unleash, the leading Open Source Feature Flag platform (that’s us! 😊) just hit 9k stars on GitHub at github.com/Unleash/unleash Thank you #Unleash community!

6 Things You’ll Find Shocking About Asynchronous Operations:

My preferences in terms of inherited code: 1) Code that was anticipating likely vector of change 2) Naive code that was not anticipating any change 3) "Extensible" code that was anticipating every possible vector of change

This is what 1 year of doing open-source looks like. Lots of small commits + frequent reviews.

Forget about traditional WebPerf metrics like LCP, TTFB, TBT. After skimming through tonsky.me/blog/js-bloat/, I've come up with a new metric for a bloated JS bundle: BTP - Bigger Than Pornhub.

World Mental Health Day came early this year #metadown

When updating components behind a feature flag, it's best to rename the old component and retain the original name for the new development to preserve git history.

My code goes to production almost every day. I love the confidence from my progressive delivery setup: * Progressive deployment (canary deployment with Kubernetes release channels operator) * Progressive release (feature flags controlled releases with Unleash)

Change Requests for feature flags are like Pull Requests for code changes. My latest blog post: getunleash.io/blog/feature-f…

The recent #CrowdStrike incident reminds us why companies should seriously consider progressive delivery at deploy time (canary deployments) and at runtime (feature flags).

Honored to see our work on Unleash acknowledged by the Thoughtworks Technology Radar! What makes this especially meaningful is that you can’t buy your way into the Radar—it’s based on real practitioner insights. 🙌 thoughtworks.com/radar/tools/un…

One of the most satisfying results of impact mapping? Addressing behavior changes with deliverables that don’t require writing a single line of code. Winning at software development is all about outcomes, not output.

Picked up a great habit from my colleagues at Unleash: using Grafana/VictoriaMetrics to guide day-to-day development. Spent 20% of this week figuring out what to visualize, creating metrics, and setting up charts to showcase the impact of our deliverables.

Account sharing might be fine for less critical systems, but when it comes to a feature flag platform, individual accounts are essential. getunleash.io/blog/stop-shar…

My favorite 10 books from last year, in no particular order. #GoodreadsYearinBooks goodreads.com/user/year_in_b…

Guillermo Rauch Vercel Next.js Love seeing how much value you get from feature flags! One thing I’m curious about—how do you manage the technical debt side? Flags tend to accumulate over time. At Unleash, we see customers creating 2 flags for every 1 they remove. How do you keep things clean?