Thanks for the session however its not clear to me as how the switch or toggle works is it manual effort on the deployed code Where is that i enable or disable the segments
Okay okay okay, hold on just a minute here. How is this guy writing backwards without any difficulty? He is behind the glass writing out words that are in the right orientation to the viewer.
Great explanation, thanks! but how can we implement that? these "IF" statements are outside the application right? I appreciated additional info, thanks!
I would assume you would use environment variables or a json file and set features to true or false. Using an environment variable makes sense based off what he said about these values should be contained outside the code so it can change with the environment.
I am a complete beginner to computer science and I'm interested in learning more about CS concepts. Is this video a part of a series or IBM is making these videos randomly? Please let me know if this video is a continuation of a series. Thanks
Hey, no direct experience with feature flags here but i suppose you would load and evaluate them at runtime from a modifiable source like a config file or a specific db table, like you would do with regular settings or translation files for example. Hope this helps
Hello there! While segmentation in this video allows you to send different variants of a feature to different users, A/B includes an additional element of usage analytics to decide which feature variant is most desirable to users or creates more traffic/interaction.
but how, if a code is in production ,the code needs to be redeployed inorder to get the toggled state to get updated right ? if there is a switch thats not practical !
The code testing that the feature is enabled before the application executes any feature-specific code has to be deployed of course, but the flags' enabled state themselves can be loaded externally via config files, or remotely by the application via an http endpoint, for example. You start by deploying the application with the feature initially disabled, and then enable it remotely whenever you're ready. A feature flag system is very flexible as it can let you turn on the feature to specific users and keep it off for other users, or turn a feature on/off at a specific date and time (think special holiday events), and all sorts of other helpful things. This is notably useful for testing that the feature works in a real-world environment, enabling the feature only for QA testers at first, and then rolling it out to your real users without needing them to update your app once it's been thoroughly tested. Or for turning the feature off *immediately* if a major issue is found with it.
How would refactoring work with feature flags? Would that feature be essentially turned off when it’s being worked on? Would you have multiple versions of the same class?
Imagine this scenario: You have two classes that implement the same contract/interface. With a feature flag, you can decide which implementation of the same function to call (from either class)
Feature flags are a great way to test something out in production but a real pain to develop, especially when the codebase is not written using sound design principles.
The fact that he might be writing in mirror view is insane.
Yup, I'm so distracted by this that I'm going to have to watch the video a second time to get the actual content.
i think its mirrored afterwords, in the edit
They should have used a video flipping feature flag
Thanks for the session however its not clear to me as how the switch or toggle works is it manual effort on the deployed code Where is that i enable or disable the segments
I love the explanation, really simple.
How did you learn to write backwards so well?
We didn't! 😉 We shared some behind making of our videos on the Community page, check it out here 👉
ibm.co/3kWnrvf 😉
Okay okay okay, hold on just a minute here. How is this guy writing backwards without any difficulty? He is behind the glass writing out words that are in the right orientation to the viewer.
Search on "lightboard videos".
Great explanation, thanks! but how can we implement that? these "IF" statements are outside the application right? I appreciated additional info, thanks!
I would assume you would use environment variables or a json file and set features to true or false. Using an environment variable makes sense based off what he said about these values should be contained outside the code so it can change with the environment.
I am a complete beginner to computer science and I'm interested in learning more about CS concepts. Is this video a part of a series or IBM is making these videos randomly? Please let me know if this video is a continuation of a series. Thanks
which feature flag service do you recommend
Are there any opensource tools for feature flagging?
IMHO, You can leverage OPA to do this beautifully.
Excuse me but is this man writing mirrored?
No, he is writing in a normal way, but the video is mirrored in the editing software
04:46 to 5:05 - flip it off, fix it, turn it back on, .....all this is done without a deployment. how is this possible?
Hey, no direct experience with feature flags here but i suppose you would load and evaluate them at runtime from a modifiable source like a config file or a specific db table, like you would do with regular settings or translation files for example. Hope this helps
Thank you for your explanations. Would like to understand more about how to integrate these feature flags with application code?
The segment part is A/B Testing, isn't it?
Hello there!
While segmentation in this video allows you to send different variants of a feature to different users, A/B includes an additional element of usage analytics to decide which feature variant is most desirable to users or creates more traffic/interaction.
Nicely explained, thanks!
but how, if a code is in production ,the code needs to be redeployed inorder to get the toggled state to get updated right ? if there is a switch thats not practical !
The code testing that the feature is enabled before the application executes any feature-specific code has to be deployed of course, but the flags' enabled state themselves can be loaded externally via config files, or remotely by the application via an http endpoint, for example.
You start by deploying the application with the feature initially disabled, and then enable it remotely whenever you're ready.
A feature flag system is very flexible as it can let you turn on the feature to specific users and keep it off for other users, or turn a feature on/off at a specific date and time (think special holiday events), and all sorts of other helpful things.
This is notably useful for testing that the feature works in a real-world environment, enabling the feature only for QA testers at first, and then rolling it out to your real users without needing them to update your app once it's been thoroughly tested. Or for turning the feature off *immediately* if a major issue is found with it.
You nailed it. Thanks for sharing.
Good job!!!!, nice explanation, Thank you for sharing
Thanks for watching, Nuwan! Glad you liked it. 🙂 You can subscribe for more videos like this.
How would refactoring work with feature flags? Would that feature be essentially turned off when it’s being worked on? Would you have multiple versions of the same class?
Imagine this scenario: You have two classes that implement the same contract/interface. With a feature flag, you can decide which implementation of the same function to call (from either class)
Feature flags are a great way to test something out in production but a real pain to develop, especially when the codebase is not written using sound design principles.
That’s why companies such as LaunchDarkly.com exist (and what IBM is using).
When you are putting it in production..it's alright deployed right ?
Hi Satish,
That is correct. The feature is deployed but not active/viewable until you toggle it on.
who has the authority to turn on/off the toggle? Is that done using a tool like Istio? or users have a button on their UI to toggle?
@@jibin7277 the application developers are responsible for turning the features on or off. More specifically a liveOps team.
It must be very difficult to write all these codes backwards :o
See ibm.biz/write-backwards
Or as we called them in my day, if statements.
Testing in production sounds like a terrible idea
The white guy has to be careful not to get his face behind the text. 😆
The video is unwatchable for me because of the squeaky marker, I really wanted to learn about feature flags
I literally don't hear the marker....
Very happy 😍💋 💝💖♥️❤️
Tks
OMG 😍💋 💝💖❤️
First