home.social

#featureflags — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #featureflags, aggregated by home.social.

  1. Ever wanted someone to do the work and clean up any stale feature flags in your code base. Here you go

    hyphen.ai/docs/changelog/promp

    #featureflags #ai #development

  2. Ever wanted someone to do the work and clean up any stale feature flags in your code base. Here you go

    hyphen.ai/docs/changelog/promp

    #featureflags #ai #development

  3. Ever wanted someone to do the work and clean up any stale feature flags in your code base. Here you go

    hyphen.ai/docs/changelog/promp

    #featureflags #ai #development

  4. Ever wanted someone to do the work and clean up any stale feature flags in your code base. Here you go

    hyphen.ai/docs/changelog/promp

    #featureflags #ai #development

  5. Ever wanted someone to do the work and clean up any stale feature flags in your code base. Here you go

    hyphen.ai/docs/changelog/promp

    #featureflags #ai #development

  6. Unleash: Feature flags in PHP

    Feature flags (also known as feature toggles) let you enable or disable specific features or code paths at runtime without deploying new code. In this article, we'll explore Unleash, my favourite open-source tool for managing feature flags efficiently.

    chrastecky.dev/programming/unl

  7. Unleash: Feature flags in PHP

    Feature flags (also known as feature toggles) let you enable or disable specific features or code paths at runtime without deploying new code. In this article, we'll explore Unleash, my favourite open-source tool for managing feature flags efficiently.

    chrastecky.dev/programming/unl

  8. Unleash: Feature flags in PHP

    Feature flags (also known as feature toggles) let you enable or disable specific features or code paths at runtime without deploying new code. In this article, we'll explore Unleash, my favourite open-source tool for managing feature flags efficiently.

    chrastecky.dev/programming/unl

  9. In this session, I'm going to walk you through a quick demo of leveraging [Conditional] capability in C# to enable and disable blocks of code in your program seamlessly and natively.

    Check it out here today!

    #csharp #dotnet #conditional #featureflags

    youtube.com/watch?v=4wHegx1Xy4

  10. We just released enhanced editing for our feature flag service at Hyphen (hyphen.ai):

    - Syntax highlighting for improved readability
    - Line numbers for easier debugging and collaboration
    - Collapsible sections for navigating large or deeply nested JSON objects
    - Improved formatting and validation feedback

    docs.hyphen.ai/changelog/enhan

    #featureflags #development #engineering

  11. So they pointed a digital clairvoyant named Claude Code at a bunch of code repositories and it chose... to DIY everything? 🚀🔧 Apparently, when asked for feature flags, it builds its own config system out of sheer stubbornness—because why use tools when you can reinvent the wheel on every project? 🤦‍♂️ CustomDIY FTW!
    amplifying.ai/research/claude- #digitalclairvoyant #DIYcoding #featureflags #customtools #reinventthewheel #HackerNews #ngated

  12. Feature flags are not booleans.
    They are runtime decisions.

    In this article, I walk through building a production-grade feature flag system in Quarkus:
    – database-backed flags
    – security-aware evaluation
    – runtime toggles without redeploys
    – a Qute UI that shows what’s actually enabled

    If you’ve ever shipped a feature “disabled by config” and regretted it later, this one’s for you.

    the-main-thread.com/p/feature-

    #Java #Quarkus #SoftwareArchitecture #FeatureFlags #BackendEngineering

  13. Apple sta preparando nuovi prodotti: AirTag 2 per 2025, AirPods con localizzazione avanzata 2026, Vision Pro con spatializer, Health+ AI e Siri potenziata. 🚀📱

    #apple #featureflags #tecnologia

  14. Hardcode feature flags: In praise of a simple system for a useful and prod-sensitive feature. Complex feature flag systems often fail.
    code.mendhak.com/hardcode-feat
    #featureflags #programming #simplicity #+

  15. Ah yes, the 🪣 Bucket Linear Agent, the latest attempt to make "dev" life easier by throwing indecipherable jargon at the real problem: developers still have to write code. 🖥️✨ Meanwhile, we're promised a utopia where feature flags are as easy to clean up as the crumbs in your keyboard... but only if you use every tool under the sun. 🌞🤦‍♂️
    bucket.co/blog/building-the-bu #BucketLinearAgent #DevLife #CodeJargon #FeatureFlags #TechUtopia #HackerNews #ngated

  16. 🚀 Want to ship faster without breaking things?
    Watch Ahamed Safnaj at #FOSSASIASummit2025 to explore how feature flags can transform your development workflow. Learn how they decouple deployment from release, enabling safer rollouts, better risk control, and continuous delivery without user disruption.

    🔗 Click here youtu.be/NlzpIJ0D3sE to watch on the FOSSASIA YouTube channel!
    #DevOps #FeatureFlags #ContinuousDelivery #OpenSource #FOSSASIA

  17. Управляем фичами: Feature Toggles в GitLab

    Привет, коллеги! Сегодня мы рассмотрим одну из самых полезных практик, которая спасла мне не один проект — Feature Toggles в GitLab CI/CD. Это те самые переключатели, которые позволяют активировать или деактивировать функции без повторного развертывания кода.

    habr.com/ru/companies/otus/art

    #gitlab #git #featureflags

  18. 🚀 Excited to share "Flip the Switch: Modern Software Development with Feature Flags" – a guide to faster, safer innovation! I wrote the foreword to highlight how feature flags drive agility & modernization.

    📖: flagsmith.com/ebook/flip-the-s

    @GetFlagsmith

  19. Enhancing API Stability with Feature Flags

    nordicapis.com/enhancing-api-s

    "While often associated with frontend toggles, feature flags offer powerful capabilities for backend API management as well." -- #GloriaWang

    #api360 #apiDesign #featureFlags

  20. I believe #featureFlags (as implemented with services like #launchDarkly) are an #antiPattern; they are just a second set of #environmentVariables that need to be tested against. Just use env vars. Too many? There's your problem! #12factor

  21. I believe #featureFlags (as implemented with services like #launchDarkly) are an #antiPattern; they are just a second set of #environmentVariables that need to be tested against. Just use env vars. Too many? There's your problem! #12factor

  22. I believe #featureFlags (as implemented with services like #launchDarkly) are an #antiPattern; they are just a second set of #environmentVariables that need to be tested against. Just use env vars. Too many? There's your problem! #12factor

  23. I believe (as implemented with services like ) are an ; they are just a second set of that need to be tested against. Just use env vars. Too many? There's your problem!

  24. I believe #featureFlags (as implemented with services like #launchDarkly) are an #antiPattern; they are just a second set of #environmentVariables that need to be tested against. Just use env vars. Too many? There's your problem! #12factor

  25. Gave my first talk since The Pancake last night - an intro to #featureflags and #OpenFeature.

    A small crowd, but lovely and very engaged! It feels like feature flagging is a perennially interesting topic - most teams are doing it, most are looking for ways to get better at it.

  26. blurghed: adding feature flagging to a node app using OpenFeature.

    Get started with a simple hard-coded feature flag provider in literally a couple of minutes, with the option of a seamless future upgrade to the full-blown feature flagging frameworks that integrate with OpenFeature.

    blog.thepete.net/blog/2023/03/

    #FeatureFlags #openfeature #node #express #javascript #cncf

  27. Do you use #featureflags ? With #openfeature it is a one-line change to switch from in-house to vendor. OpenFeature is tightly integrated with #opentelemetry so everything is #observable by default. docs.openfeature.dev for more info

  28. blurghed: what makes client-side #FeatureFlags different from server-side, and how we're extending the #openfeature API to support client-side flags:

    docs.openfeature.dev/blog/cate

    TL;DR:

    1) on the server-side the evaluation context for flagging decisions is highly dynamic (each request is for a different user), vs client-side where it's *mostly* static.

    2) on the client, feature flag evaluation is expensive/slow.

    This means on the client flags are typically pre-evaluated ahead of decision time