text stringlengths 0 2.29k |
|---|
[2946.90 --> 2948.00] Yeah, there you go. |
[2948.00 --> 2948.56] The next Kaizen. |
[2948.96 --> 2949.70] The next Kaizen. |
[2950.26 --> 2950.62] Yes. |
[2950.90 --> 2952.26] Okay, so we have it on record. |
[2952.26 --> 2953.30] There will be another Kaizen. |
[2953.52 --> 2954.10] Oh, yes. |
[2954.16 --> 2955.22] Not just a hope and a dream. |
[2955.38 --> 2956.36] We just need to figure out where. |
[2957.36 --> 2962.04] So if I understand this correctly, Jared, you've done this work, but you haven't done it in production. |
[2962.22 --> 2966.68] So you need a way to test in production, essentially, to see how it responds. |
[2967.36 --> 2969.16] I spiked it out on a branch. |
[2969.70 --> 2972.46] And then it was just like, okay, this is certainly feasible. |
[2972.46 --> 2977.86] And I did some rudimentary benchmarking of that branch just to make sure it's not crazy dumb. |
[2977.86 --> 2981.64] And then I'm like, okay, this is feasible. |
[2982.44 --> 2985.44] And I know how to bring this into like official code. |
[2985.54 --> 2993.14] Like I can definitely transition what I coded into like, or even just rewrite it in a way that's maintainable if we decide to do it. |
[2993.14 --> 2997.94] But I really like to know if it's going to be really dumb or just kind of dumb. |
[2998.32 --> 3007.14] You know, like I feel like it's just dumb enough that it just might work, you know, and be so simple and solve a problem in a way that's just like awesomely dumb. |
[3007.14 --> 3010.00] But I don't want it to be so dumb that it's not going to work. |
[3010.70 --> 3012.60] That's the real spirit of shipping. |
[3012.68 --> 3012.86] Yeah. |
[3013.00 --> 3013.14] Right. |
[3013.18 --> 3015.82] We literally have to get it out to see if it works. |
[3015.84 --> 3016.72] Like what happens? |
[3017.04 --> 3019.36] And then I was like, well, what I lack is metrics. |
[3020.14 --> 3025.66] If I can observe it for a few hours, get some confidence, leave it in or be like, oh, cow, that was not. |
[3026.22 --> 3029.52] It worked great in dev, but it's not going to work with a real load. |
[3029.70 --> 3031.94] You know, I have a question for Adam. |
[3031.94 --> 3038.56] So Adam, I think this may be the moment to tell us again about the benefits of feature flags. |
[3039.30 --> 3040.20] I almost mentioned it there. |
[3040.28 --> 3042.62] I was like, I don't want to have egg on my face, but I mentioned in feature flags. |
[3042.74 --> 3047.66] I know Jared has sort of been a resistant to some degree against it, but there may be a simpler way to do this. |
[3047.70 --> 3050.02] But I think that that's essentially what you want to do. |
[3050.06 --> 3053.08] You want to test this in production on a limited set of users. |
[3053.18 --> 3055.16] So it could be a scope to admins only, for example. |
[3055.42 --> 3056.84] No, because I want to load test it. |
[3056.94 --> 3059.84] I want the full load is my issue. |
[3059.84 --> 3062.78] But it could be like maybe 50% of the requests, you can compare them. |
[3063.12 --> 3065.56] So 50% of the requests, 50-50. |
[3065.66 --> 3066.04] A threshold. |
[3066.28 --> 3072.82] Going to the old one, 50 to the new implementation and see how do they compare over the course of maybe a few days. |
[3073.14 --> 3073.92] Yeah, we can do that. |
[3074.30 --> 3076.14] So Adam, how do we get feature flags? |
[3076.32 --> 3076.82] What do you think? |
[3078.28 --> 3079.40] Where do you stand on that? |
[3079.76 --> 3085.04] Well, if we're doing 50-50, can't we just do like an if statement with like random divided by two? |
[3085.94 --> 3086.34] Sure. |
[3087.60 --> 3087.96] Sure. |
[3087.96 --> 3092.18] If it's an even second, do this. |
[3092.42 --> 3094.54] And if it's an uneven second, do the other thing. |
[3094.96 --> 3099.64] If it's an imperial unit or if it's the metric system. |
[3099.76 --> 3101.86] Is this the metric system or which system are we going to use here? |
[3102.62 --> 3104.32] Luckily, seconds only exist. |
[3104.32 --> 3107.82] I know Adam's been keen on feature flags. |
[3107.96 --> 3111.32] I feel like this is his big moment to introduce some sort of subsystem. |
[3111.46 --> 3112.12] I think so too. |
[3112.48 --> 3114.78] I mean, I don't feel like I have a system to pitch here. |
[3115.20 --> 3117.02] No, I remember the conversation, Jared. |
[3117.12 --> 3118.56] That's why I keep going back to it. |
[3119.02 --> 3122.48] Because we didn't have a good answer for Adam and we were both against it. |
[3122.54 --> 3125.68] So maybe now it's coming back and maybe now it's a yes. |
[3126.02 --> 3128.02] Because it was a no, definite no back then. |
[3128.02 --> 3128.82] We were premature. |
[3129.28 --> 3130.40] When I try to pitch... |
[3130.40 --> 3130.70] Feature flags? |
[3130.94 --> 3135.02] The insider story here, listeners, is there was... |
[3135.54 --> 3138.02] My initial pitch for us using feature flags was... |
[3138.02 --> 3140.44] Fell on deaf ears essentially because we were premature. |
[3140.62 --> 3141.90] We just didn't have the needs for it. |
[3142.32 --> 3143.76] We were trying to find a use for it. |
[3143.86 --> 3148.98] And if you follow Kaizen and ship it and what we've done, then you know our application is pretty simple. |
[3149.56 --> 3151.18] We don't have a lot of developers developing on it. |
[3151.18 --> 3157.80] So there's not a real need for, you know, any immense feature flags, feature and or service to use. |
[3158.38 --> 3159.94] Launched Darkloos are friends for a while there. |
[3160.52 --> 3162.40] I'd still say they're friendly, but they're not friends. |
[3162.56 --> 3164.14] We're not working with them directly anymore. |
[3164.70 --> 3170.48] We do have a new sponsor coming on board, DevCycle, which is in the feature flag business. |
[3171.06 --> 3175.52] Which, you know, if you wanted to use it for this one instance, I'm sure we could do something. |
[3175.68 --> 3177.02] So, I mean, there is an opportunity there. |
[3177.26 --> 3179.00] But that would be my pitch. |
[3179.00 --> 3184.48] I feel like, you know, if it's just this one-off though, then the if statement probably works. |
[3185.02 --> 3187.82] Well, I'll let you know when I get this far. |
[3187.98 --> 3191.38] What we need first, I think, is the observability. |
[3192.36 --> 3196.22] Because either way, if we do it 50-50, we want to see both results. |
[3196.50 --> 3196.72] Of course. |
[3196.82 --> 3202.54] And so right now, I can't see any results besides sit there and stare at the log files and look at the request responses. |
[3203.54 --> 3206.96] Which was a side effect, actually, of one of our recent changes. |
[3207.08 --> 3208.50] Our log files just stopped logging. |
[3208.50 --> 3209.24] I got it fixed. |
[3209.32 --> 3210.24] But that was funny. |
[3210.60 --> 3211.32] So I'm like, wait a second. |
[3211.38 --> 3212.28] There aren't any logs. |
[3212.40 --> 3213.88] How can the changelog not log? |
[3213.98 --> 3214.24] Right? |
[3214.36 --> 3217.24] It's just like against the laws of nature, essentially. |
[3217.52 --> 3220.50] Well, I'm not going to get blame that one on the air. |
[3221.02 --> 3222.44] Because I don't want to embarrass Gerhard. |
[3222.60 --> 3224.34] But I fixed it. |
[3224.36 --> 3224.76] That's okay. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.