Deleted Comment
On one hand, LLMs do require significant amounts of compute to train. But the other hand, if you amortize training costs across all user sessions, is it really that big a deal? And that’s not even factoring in Moore’s law and incremental improvements to model training efficiency.
It doesn’t really matter how you manage changes to feature flags, but using version control gives you a couple of nice benefits:
* gives developers the opportunity to describe their change
* let’s you roll back a problematic patch
* blame and bisect problematic patches
Ideally, you should also be able to see your feature flag changes in prod much faster than it takes to cut a release. You need this in order to be able to quickly roll back bad features.
> What feature flag tool do you use?
See https://engineering.fb.com/2017/08/31/web/rapid-release-at-m...
_Given_ that I want to study React in the woods, how should I do it?
Whether or not to study React in the woods is completely irrelevant.
Ad hominems are against TOS.
Answering the question is irrelevant if it’s the wrong question to begin with. And for the wrong circumstances (ie if this is a family vacation) can be counter-productive. It’s far more productive to zoom out, ask why the author is asking for advice to study react on vacation, and address that instead. Consider this as you advance your career past recent college grad / swe1 :)
This is my current battle.
I introduced feature flags to the team as a means to separate deployment from launch of new features. For the sake of getting it working and used, I made the mis-step of backing the flags with config files with the intent to get Launch Darkly or Unleash working ASAP instead to replace them.
Then another dev decided that these Feature Flags look like a great way to implement permanent application configs for different subsets of entities in our system. In fact, he evangelized it in his design for a major new project (I was not invited to the review).
Now I have to stand back and watch as the feature flags are being used for long-term configurations. I objected when I saw the misuse- in a code review I said "hey that's not what these are for"- and was overruled by management. This is the design, there's no time to update it, I'm sure we can fix it later, someday.
Lesson learned: make it very hard to misuse meta-features like feature flags, or someone will use them to get their stuff done faster.
I don't see the problem with developers using flags for configuration as a stopgap until there's a better solution available.
Your life is essentially a compilation of what captures your attention. Embracing this perspective, any entity auctioning off your attention to the highest bidder is trading away a part of your life.
People don't understand what this means. They also don't understand how cynical this is in the context of a search engine. I don't have a solution to this, but man, its horrible.
I've also been banned one day for posting ads for my pictures. Just portraits, nothing special.
I got zero explanation and could not recover my ad credits.
More recently I was shadow banned for including links to YouTube on my fb post. Got a reach of 21, where it was usually above 1000. My page didn't recover yet.
It's time to let meta die.