π™Ώπš›πš˜πšπš›πšŠπš–πš–πšŽπš›, πšπš›πšŠπš’πš—πšŽπš›, πšπš›πš˜πšžπš‹πš•πšŽπš–πšŠπš”πšŽπš›, πšŒπš‘πšŠπš—πšπšŽ πšŠπšπšŽπš—πš.

π™Ίπš›πšŠπš”πš˜πš , π™Ώπš˜πš•πšŠπš—πš
Joined January 2009
π™ΌπšŠπšπšŽπšžπšœπš£ π™Ίπš πšŠπšœπš—πš’πšŽπš πšœπš”πš’ retweeted
Replying to @rauchg @vercel @nextjs
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?
3
8
246
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…
1
108
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.
3
150
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.
1
4
166
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…
4
168
The recent #CrowdStrike incident reminds us why companies should seriously consider progressive delivery at deploy time (canary deployments) and at runtime (feature flags).
2
166
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)
1
4
211
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.
3
341
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.
2
251
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
322
π™ΌπšŠπšπšŽπšžπšœπš£ π™Ίπš πšŠπšœπš—πš’πšŽπš πšœπš”πš’ 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!
4
1
13
825