This video took 6,089 lines of code to bring to life. Here’s the breakdown if you’re curious: S1: 507 S2: 386 s3: 285 S4: 546 S5: 771 s6: 414 S7: 531 s8: 572 s9: 783 s10: 598 S11: 256 S12: 219 s13: 221 And it's built using Motion Canvas - motioncanvas.io/
They literally get paid with stock, if discord makes more money their stock is worth more. They can then sell it when discord goes public and get paid. smh
@@kikisbytesI didn’t find it particularly hard to understand, and I feel like you did a pretty decent job of explaining compression. I do that wish you went into more depth about what context is and how it’s used to improve the efficiency of streaming compression, though. Otherwise I thought the video was great!
Its fascinating to see what a big company does to implement a new feature or a fix. So many factors, so many elements to check for. Great video. Thanks.
No. It's fascinating to see how people are unaware of zstd existing that was released 10 years ago and I haven't seen anyone who has every worked with logs being unaware of it and actually using gz/zlib for anything where bandwidth/compressed file size is actually important
I love the quality and pace of this video - engaging explanation of the underlying concepts, use case story, test outcomes, deployment strategy...all explained in 8 minutes! Edit: Plus citations and Chapter markers in description too! 🥳
0:08 costs per what? Week? Day? Hour? It's not cumulative, it's not monthly, the points don't line up with months and looks like it's every 2 weeks but that's a weird unit of time
Thank you for the feedback! I usually make the animations of how I envision the scene to look like then I try to match it with the voice recording. I find that this 2-3x my development speed. This means that sometimes the animation can be fast because the voice recording section is a lot shorter than I had anticipated. Will try my best to leave another second or two for you to absorb the graphs.
