It's OK to hardcode feature flags (2025)

(code.mendhak.com)

7 points | by biscuits1 1 hour ago

5 comments

  • aksappy 1 minute ago
    Unclear how the arguments against feature flags can be used to justify hardcoding them or using a JSON file to manage them. Feature flag decisions are at the end of the day, tradeoffs to solve a problem that may occur for another person at a different place/time. If you are a solo developer, hardcode, use bytes or mail your feature flags - it does not matter. If you are not, there is a lot to take care of beyond a single hardcoded json file.
  • Xirdus 4 minutes ago
    Hardcoding feature flags prevents you from deploying the same build with different flag sets side by side and comparing results. Depending on the nature of the project, it might be irrelevant or it might be a deal breaker. Especially in cloud environments, it's usually the latter. And everything is in the cloud nowadays.
  • mhog_hn 19 minutes ago
    note that this is a "pre-november 2025 opus 4.5" post folks
  • michael_luog 56 minutes ago
    [dead]
  • devecycle-marke 8 minutes ago
    [flagged]