text stringlengths 0 2.29k |
|---|
[4488.80 --> 4490.06] You did not get to do a good job. |
[4490.28 --> 4493.20] All I said was, you don't have to go home, but you can't stay here. |
[4493.20 --> 4495.88] Well, that's what happened in the one that shipped. |
[4496.14 --> 4496.40] Ah. |
[4496.54 --> 4497.94] Behind the scenes, it was worse. |
[4498.24 --> 4498.98] I'm just messing with Jared. |
[4499.04 --> 4500.18] I'm just being silly. |
[4500.34 --> 4501.32] I don't even believe you. |
[4501.44 --> 4507.20] With all this time that I'm going to have from not shipping a Ship It episode every week, |
[4507.52 --> 4508.74] do you know what I'm going to do instead? |
[4509.28 --> 4510.98] I'm going to go Dan Tan. |
[4511.44 --> 4511.76] Ah. |
[4512.92 --> 4513.86] That's what's happening. |
[4514.82 --> 4515.64] Dan Tan. |
[4516.28 --> 4517.16] Comes again. |
[4517.16 --> 4517.24] Dan Tan. |
[4517.44 --> 4519.28] Every week, I'll go Dan Tan. |
[4520.44 --> 4521.08] Dan Tan. |
[4522.14 --> 4523.24] So that's what's up. |
[4523.82 --> 4524.54] Oh my gosh. |
[4524.56 --> 4524.88] Love it. |
[4525.26 --> 4527.02] I got my kids saying Dan Tan now. |
[4527.24 --> 4527.76] There you go. |
[4527.84 --> 4529.04] Never telling that story again. |
[4529.20 --> 4530.00] Everyone is on it. |
[4530.38 --> 4531.22] Everyone's saying it. |
[4532.28 --> 4533.32] So that's my plan. |
[4533.58 --> 4533.90] All right. |
[4534.02 --> 4534.96] Sounds good, Gerhard. |
[4535.68 --> 4536.08] All right. |
[4536.38 --> 4536.92] Thank you. |
[4537.26 --> 4537.82] It has been good. |
[4537.88 --> 4538.22] Thank you. |
[4538.36 --> 4539.08] Always a pleasure. |
[4539.62 --> 4540.44] There will be a next one. |
[4541.00 --> 4541.98] Two and a half months away. |
[4542.30 --> 4542.74] Right? |
[4543.08 --> 4543.52] Roughly. |
[4543.94 --> 4546.34] So I don't know exactly when, but two and a half months away. |
[4546.34 --> 4548.42] It will be warm and nice where you are. |
[4548.58 --> 4548.98] I'm sure. |
[4549.50 --> 4549.80] Yeah. |
[4549.94 --> 4550.96] I'm looking forward to that. |
[4551.52 --> 4551.76] Kaizen. |
[4552.14 --> 4552.50] Same. |
[4552.70 --> 4552.98] Kaizen. |
[4553.02 --> 4553.32] Kaizen. |
[4556.90 --> 4559.68] Thank you for tuning into another episode of Shibit. |
[4559.68 --> 4564.92] Check out our other podcasts for developers at changelog.com slash master. |
[4565.34 --> 4569.82] You can connect with like-minded developers by changelog.com slash community. |
[4570.40 --> 4572.70] Thank you all for being a great audience. |
[4573.12 --> 4575.78] I really enjoyed making all this content for you. |
[4576.22 --> 4579.86] Thank you to all the guests that have joined me on Shibit.show. |
[4580.22 --> 4582.00] I had such a great time with you all. |
[4582.52 --> 4583.28] Until next time. |
[4583.28 --> 4591.16] Game on. |
[4591.16 --> 4593.46] Game on. |
• Delayed conversation between Gerhard Lazu and Tim McNamara finally takes place |
• Tim McNamara discusses his recent injury from a mountain bike accident and its aftermath |
• Conversation turns to Tim's work at AWS as a senior software development engineer supporting the Rust programming language |
• Tim explains the unique challenges of working in a different timezone and leading an education project for adopting Rust at Amazon |
• The benefits of using Rust in software development, including reduced memory usage and improved stability |
• The concept of "organizational inertia" where companies may resist adopting new technologies like Rust due to fear of change |
• The potential for Rust to reduce energy use by 50% through more efficient coding practices |
• The comparison of CPU vs. memory usage in cloud services, with memory being a more limiting factor |
• Case studies, including AWS and Discord, which have seen significant improvements in performance and latency using Rust |
• Latency reduction through smaller CPU and memory usage |
• Importance of low latency in user experience and cost savings |
• Comparison of Rust vs Python vs Java cold start latencies |
• Benefits of using Rust for AWS Lambda functions, including faster execution and lower memory usage |
• Cost savings from reduced operational burden on service teams and lower overall system costs |
• Potential savings of hundreds of millions of dollars by adopting Rust internally |
• Benefits of using Rust for programming, including optimized performance and cost savings |
• Features of the Rust language, such as pattern matching, enums, and result types |
• Error handling in Rust, which requires explicit error checking and provides a more robust way to handle errors than languages like Go |
• The history of Rust's development, including its creation by Mozilla to address the need for faster web browsers |
• Examples of successful uses of Rust at AWS, including the reimplemented shard store for S3, which has been formally verified as resistant to most classes of errors |
• Amazon S3 and other AWS services are using Rust to improve performance and efficiency |
• Using Rust can reduce energy usage and save money for companies like Amazon, with a goal of saving $100 million per year |
• Rust is not a complete solution, but it's a good partial answer to the problem of software bloat |
• The cost savings from using Rust are a byproduct of developing software that meets expectations for reliability and performance |
• Rust has its limitations, including being more restrictive and less flexible than other languages like Python, making it less well-suited for certain tasks. |
• Tim McNamara wrote his book "Rust in Action" after noticing a trend towards shallow technical literature |
• He aimed to write a comprehensive book on learning Rust from scratch without relying on existing resources |
• The book features large examples that teach the reader how to implement real-world applications and systems, such as a database, CPU emulator, NTP client, and operating system kernel |
• Tim encountered challenges in writing the book due to its unique approach and had to trim down examples to focus on one feature at a time |
• The first edition received positive feedback from 90% of readers but criticism from others who preferred more traditional approaches |
• A second edition is being written with the intention of refining explanations, expanding on certain topics, and maintaining the book's distinct approach. |
• Concerns about expert bias and blindness in a Rust programming project |
• Importance of considering the reader's level of knowledge when writing |
• Discussion on reducing complexity by breaking down large problems into smaller, incremental changes |
• The concept of "clicking" as an analogy for finding solutions to complex problems |
• The importance of individual actions and small changes towards solving significant problems |
• Upcoming event: Rust Nation UK conference (February 16th-17th) |
**Gerhard Lazu:** Tim. Fourth time lucky. |
**Tim McNamara:** I'm so sorry, Gerhard. Honestly, I wanted to be there the first time, I wanted to be there the second time, I got injured, I couldn't come on the third time... But now I'm here, and I want to know that -- like, my time is yours. Yeah, feel free to use it however you think would be most suitable. |
**Gerhard Lazu:** Well, I have to say thank you very much, Tim, to our listeners. That's how badly I wanted to have this conversation. I tried until it happened. Okay? And we have been delaying it, I think by a few weeks, and we spoke about it briefly in September, and then holidays happened, and then all sorts of othe... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.