Tim is one of the world's leading Rust educators and runs a tech consultancy: accelerant.dev.
Tim learned to code to assist with humanitarian disasters around the world from New Zealand. He's been tinkering with computers ever since.
Previously the global head of Rust language education at AWS, he is the lead content creator for the official Rust training program offered by the Rust Foundation. He has held positions within AWS, Canonical, a number of data science consultancies, and more. Tim's the author of Rust in Action.
Tim's academic background isn't compsci or statistics. He holds a Master of Public Policy. His hope is that this can be a sign to others from non-traditional backgrounds that their place in the technology industry is valid and valued.
Tim releases most of what he produces on his own time under an open licence. As well as writing code, he makes occasional contributions to iNaturalist, OpenStreetMap and Wikipedia.
You should have made it clear that this is a teaser for a full interview. I happened to expect it so i checked the description. Make it easier to find the full vid
I think that no video is near to the brown university book explanation. It's hard way of learning. But it's also nice to do some variation in the learning style.
Hi Tim, Trying to get a Rust on AWS Workshop written. Aimed at helping people of all levels get started writing rust and using the Rust sdk for AWS. No need to twist my arm to come to NZ and visit my sister as well.
Nice Interview. Thank you. But there seems to be some problem with varying loudness. I get the impression the interviewee doesn't sit tight or something of that kind... ?
This is partially a function of not being a consistent distance from the microphone, but mostly it's due to my lack of audio engineering prowess. As the podcast is at a very inchoate stage and isn't being run on a commercial basis, I don't want to prevent it from succeeding by spending too much money or time up front. When we have established 10k listeners/episode and it's a confirmed commercial success, I'll be happy to release a remastered version :D All of the WAV files (and MP4 video files) are sitting there waiting for someone who knows what they're doing. Thanks for your comment Paul. Feedback like this helps tremendously.
I am hoping to keep the price near $400 + GST, which will be about half the price of equivalent conferences in USA and Europe for a similar (better?) quality level. It will mostly depend on whether I can secure an anchor sponsor or 7.
great video would love to see more of this, trying to understand how to read a rust codebase without getting bogged down or reading things line by line tediously is hard for newbies
Yes it would be. It's possible that the byte patterns that we are matching here are part of some other character, which might cause them to become invalid.
Ive been watching Rust content for so long that my mind went to Copy just before you wrote Oof(), when I code in Rust, this knowledge just goes somewhere else in my brain and is unaccessible.
@@timClicks I'm building a TUI Speed reader with Ratatui, something similar to Stutter Chrome extention but with the intent to eventually integrate with vim, it's an ADHD reading aide
Didn’t finish the whole video yet, but you’re supposed to store the MEAN not the average… Edit: My bad, I read "mean" and my brain understood it as "median". Sorry about that.
What's the difference? From what I gathered they're pretty much identical. It seemed to me that they differ in some technical math terms regarding their history, but that's not not really important in the broader sense. "the mean is the average of all the data values"
@@Gramini I'm sorry, you're absolutely right. For whatever reason I read "mean" and I understood it as "median". A median (which in this case it is NOT, my bad) would change the implementation quite significantly.
The notion that other languages don’t have lifetimes for their variables is obviously false. It’s erroneous code to return references to stack variables, leak memory by stealing from a smart pointer and not doing free/delete yourself, or dereference an iterator whose underlying container has been destroyed.
This is super timely as I am simulating a 2D non ideal gas at the moment and new to Rust! I have a simulation in Python but it is too slow for lots of particles. Hoping the Rust version can handle more, faster!
