Thanks for the video! In my previous job, we used to have some "hidden" frontend features on production that would be enabled by passing some flags as query params in the URL. Not really dynamic, but it helped POs and managers test out future staff while on production.
@WebDevCody Жыл бұрын
That’s an interesting approach. Seems like a simple solution which meets your teams needs
@appel-32 Жыл бұрын
This is actually very interesting, lately I've been looking for something like this and it feels like perfect timing, every time I'm trying to implement something to my project you go out with another video with the exact thing that I'm looking for. Keep up w the content Cody!
@SeibertSwirl Жыл бұрын
Good job babe!!!!! First!
@matt_woelfel Жыл бұрын
great video, do you think it'd ever get cumbersome managing more than a few feature flags? Or would you just remove the flag all together once everything is functioning reliably in prod?
@WebDevCody Жыл бұрын
You remove the flags at some when your app decides the feature is here to stay and it’s been turned on for everyone for a while.
@hanes2 Жыл бұрын
testing in production is what twitter does nowadays ^
@WebDevCody Жыл бұрын
😂 savage
@leonardssh Жыл бұрын
nice job
@mikedev22 Жыл бұрын
Awesome video. What theme are you using?
@WebDevCody Жыл бұрын
Bearded theme stained blue
@jora5483 Жыл бұрын
Is this thing also called deployment patterns?
@WebDevCody Жыл бұрын
Maybe idk, I know the word canary releases is a deployment strategy
@emkjuslen3 ай бұрын
do you guys use a third party plartform to handle this or you implement it your self?
@WebDevCody3 ай бұрын
We handle it ourself
@John-mj1kk Жыл бұрын
What microphone do you use?
@WebDevCody Жыл бұрын
MXL 990
@John-mj1kk Жыл бұрын
@@WebDevCody Thanks!
@innerinsights224 Жыл бұрын
How does one stay disciplined to learn coding
@WebDevCody Жыл бұрын
money to buy food with is one good type of motivation
@josersleal4 ай бұрын
feature flags = commented code = trash in codebase
@amgadtawfik7534 Жыл бұрын
Feature flags are really troublesome and wouldn't recommend following that pattern
@WebDevCody Жыл бұрын
Why is that?
@Ca-rp7bv Жыл бұрын
Try to dev in big code base that is sensitive and being used by many users, troublesome will be to not have a fast kill switch or any way to compare your results and automations for features with bugs
@amgadtawfik7534 Жыл бұрын
@@Ca-rp7bv there are design patterns like facade or versioning with microservices that can be leveraged to do just that without added complexities
@amgadtawfik7534 Жыл бұрын
@Web Dev Cody we use this pattern in one of the applications I am working on. This application is based on system events, so we have millions of transactions per day. When we experience any problem and we have 100s of feature toggles, tracing through all these toggles, Is really hectic.
@WebDevCody Жыл бұрын
@@amgadtawfik7534 why do you have 100 feature flags? You’re supposed to delete them after they are deployed for a couple of weeks