How to Avoid Technical Mistakes in a Book

Allen Wyma talks with Lily Mara, the author of the book Refactoring to Rust.

Contributing to Rustacean Station

Rustacean Station is a community project; get in touch with us if you’d like to suggest an idea for an episode or offer your services as a host or audio editor!

• Twitter: @rustaceanfm
• Discord: Rustacean Station
• Github: @rustacean-station
• Email: hello@rustacean-station.org

Timestamps

• [@1:26] - Lily’s Bio
• [@3:33] - Her blogs helped her improve her writing
• [@5:09] - How the book came to be
• [@9:34] - Knowing when to add a new language to an existing project
• [@12:07] - Tools for measuring memory usage
• [@15:04] - Garbage collection
• [@18:30] - Strongly and weakly typed languages & dynamic vs static dispatch
• [@21:13] - About the book
• [@25:40] - Go being treated like a C library
• [@27:02] - Memory allocators
• [@35:51] - When did Lily started working on the book?
• [@37:44] - Writing examples (it’s hard!)
• [@46:36] - How technical are the editors?
• [@49:00] - The Rust community is very welcoming
• [@50:14] - Publishers that are publishing Rust books
• [@52:17] - Lily’s Twitch stream for Manning
• [@53:07] - Lily’s advice for aspiring Rust developers

Other Resources

• PyO3
• Flutter Rust Bridge

Credits

Intro Theme: Aerocity

Audio Editing: Plangora

Hosting Infrastructure: Jon Gjengset

Show Notes: Plangora

Hosts: Allen Wyma