πΌππππππ£ πΊπ ππππππ πππ retweeted
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 @getunleash, we see customers creating 2 flags for every 1 they remove. How do you keep things clean?
My favorite 10 books from last year, in no particular order. #GoodreadsYearinBooks goodreads.com/user/year_in_bβ¦
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β¦
Picked up a great habit from my colleagues at @getunleash: 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.
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.
Honored to see our work on @getunleash 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β¦
The recent #CrowdStrike incident reminds us why companies should seriously consider progressive delivery at deploy time (canary deployments) and at runtime (feature flags).
Change Requests for feature flags are like Pull Requests for code changes. My latest blog post: getunleash.io/blog/feature-fβ¦
My code goes to production almost every day. I love the confidence from my progressive delivery setup:
* Progressive deployment (canary deployment with @kubernetesio release channels operator)
* Progressive release (feature flags controlled releases with @getunleash)
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.
World Mental Health Day came early this year #metadown
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.
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
πΌππππππ£ πΊπ ππππππ πππ retweeted
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!
A whirlwind tour around feature toggles from @DevoxxPL 2023. Probably my most rehearsed and polished talk ever :)
youtube.com/watch?v=kIAOizcnβ¦
Very good talk about the dark side of async code reviews by @d_stepanovic This stuff shouldnβt be controversial @DevoxxPL
No stress, itβs just a conference room. The room :) @DevoxxPL








