TMI: Talk preparations
Jun. 4th, 2013 05:48 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
timToday I worked a bit more on issue 5683 (which, for now, just means turning more of the rustpkg test cases into executable #[test] tests and not just English descriptions in a text file. We'll do something fancier later.
I attempted to figure out why my pull request for rustpkg versions failed tests on the Linux bot, but got nowhere, since the test that failed passes on my Mac, and rather than trying to remember how to ssh into one of our Linux machines, I decided to work on my talk instead.
My talk is in a little over two weeks. I got through about half the slides today, and will probably try to blow through the other half tomorrow. I mean just getting them into a rough form without any "fill this in" -- I expect to spend a lot of my time between now and June 19 working on the slides. I'm trying to turn off my inner critic and just write stuff down for now -- it's much easier to edit something that's rough than to turn nothing into something, which is what I'm doing now -- but it's hard, as usual. Also hard is striking the right balance between accessibility and realism with code examples. So far, I've found tiny examples to use from Servo, sprocketnes, and the Rust standard libraries. It's hard to find a non-trivial example that doesn't require explaining too many new concepts at once, though. So the ones I've pulled are very simple. Given that, I'm wondering how much it adds to be using real examples; I wonder if I should stick to using examples from Rust standard libraries or just make up my own examples. I originally thought the talk would be more interesting if I used examples from real Rust applications, but I just don't know if the details of those applications (not so interesting until you spend time immersed in them) justify the benefits of verisimilitude.
I attempted to figure out why my pull request for rustpkg versions failed tests on the Linux bot, but got nowhere, since the test that failed passes on my Mac, and rather than trying to remember how to ssh into one of our Linux machines, I decided to work on my talk instead.
My talk is in a little over two weeks. I got through about half the slides today, and will probably try to blow through the other half tomorrow. I mean just getting them into a rough form without any "fill this in" -- I expect to spend a lot of my time between now and June 19 working on the slides. I'm trying to turn off my inner critic and just write stuff down for now -- it's much easier to edit something that's rough than to turn nothing into something, which is what I'm doing now -- but it's hard, as usual. Also hard is striking the right balance between accessibility and realism with code examples. So far, I've found tiny examples to use from Servo, sprocketnes, and the Rust standard libraries. It's hard to find a non-trivial example that doesn't require explaining too many new concepts at once, though. So the ones I've pulled are very simple. Given that, I'm wondering how much it adds to be using real examples; I wonder if I should stick to using examples from Rust standard libraries or just make up my own examples. I originally thought the talk would be more interesting if I used examples from real Rust applications, but I just don't know if the details of those applications (not so interesting until you spend time immersed in them) justify the benefits of verisimilitude.
(no subject)
Date: 2013-06-05 10:30 pm (UTC)(no subject)
Date: 2013-06-05 10:32 pm (UTC)Next week any afternoon (Pacific time), roughly between 2:30-6, should work for me, except Wednesday. I've used Skype and Google Hangouts before, so either of those would probably work. Let me know what you prefer (feel free to email instead, catamorphism@gmail.com ) and thanks!