18
Rust for Lemmings Reading Club - Alternate Slot (18:00 UTC+1) (jlai.lu)
submitted 8 months ago* (last edited 8 months ago) by Jayjader@jlai.lu to c/learningrustandlemmy@lemmy.ml
8 comments fedilink hide all child comments

Hi all!

What?

I will be starting a secondary slot/sessions for the Reading Club, also on "The Book" ("The Rust Programming Language"). We will, also, very likely use the Brown University online edition (that has some added quizzes & interactive elements).

Why?

This slot is primarily to offer an alternative to the main reading club's streams that caters to a different set of time zone preferences and/or availability.

When ?

Currently, I intend to start at 18:00 UTC+1 (aka 6pm Central European Time). Effectively, this is 6 hours "earlier in the day" than when the main sessions start, as of writing this post.

The first stream will happen on the coming Monday (2023-03-04).

Please comment if you are interested in joining because you can't make the main sessions but would prefer a different start time (and include a time that works best for you in your comment!). Caveat: I live in central/western Europe; I can't myself cater to absolutely any preference.

How ?

We will start from the beginning of "The Book".

There are 2 options:

  1. mirror the main sessions' pace (once every week), remaining ~4 sessions "behind" them in terms of progression through "The Book"
  2. attempt to catch up to the main sessions' progression

I am personally interested in trying out 2 sessions each week, until we are caught up. This should effectively result in 2-3 weeks of biweekly sessions before we slow back down. I'm not doing this just for me, however, so if most people joining these sessions prefer the first option I'm happy to oblige.

I will be hosting the session from my own twitch channel, https://www.twitch.tv/jayjader . I'll be recording the session as well;~~this post should be edited to contain the url for the recording, once I have uploaded it~~ here's a youtube link to the recording of the session: https://youtu.be/gQDO_UtXKBg

Who ?

You! (if you're interested). And, of course, me.

top 8 comments
sorted by: hot top controversial new old
[-] Jayjader@jlai.lu 4 points 8 months ago* (last edited 8 months ago)

Clarification: the "six hours earlier" is only with regards to the time of day, it does not include the actual day on which the stream occurs.

Notably, @sorrybookbroke@sh.itjust.works 's streams are currently on Wednesdays my time / Tuesdays theirs, so in theory I am proposing to host my streams at around (24+6) 30 hours before they do.

[-] Jayjader@jlai.lu 3 points 8 months ago

Post-stream followup: Thanks so much to everyone that showed up! It was a lot easier to just start talking into the mic knowing at least 1 person was actively listening.

We started from the very beginning of the book, and managed to finish chapter 2 after about 3 hours. Very few stumbles and almost no parts that required us to spend more than 5 minutes understanding them, so I'm not sure that this is very representative yet of the average future session. Still, the pacing seemed comfortable enough for myself and those interacting via the twitch chat that I don't plan on changing the approach much yet either.

I have uploaded the video to youtube (booo, I know, but at least it's decently-permanent free storage) and as of posting this comment youtube tells me there are around 4 hours of processing left before it's visible. I'll probably be asleep by then, but hopefully y'all will have the link in the next 12 to 24 hours. In the meantime, here's the link to the temporary recording that twitch makes ("temporary" as in will probably be deleted in a few weeks or months, beyond my control): https://www.twitch.tv/videos/2081106703

[-] Jayjader@jlai.lu 3 points 8 months ago

Having now watched the recording myself, I think the session ran a bit long. Not only is a 3+ hour timeslot difficult to fit into people's schedules, but I find that as a host I became noticeably worn out near the end. I wanted to cleanly wrap up the chapter we had already started and so pushed through at the time. For future sessions I think it will be better to aim for around two hours, or at least assess after two hours if we're still up to continuing the session.

[-] ericjmorey@programming.dev 2 points 8 months ago

Awesome! This should really help people in Europe who want to follow along.

I think trying to catch up would be a mistake unless the people who join are already at pace with the original schedule.

[-] Jayjader@jlai.lu 2 points 8 months ago* (last edited 8 months ago)

I think trying to catch up would be a mistake unless the people who join are already at pace with the original schedule.

Could you elaborate on how it would be a mistake? I was thinking there might be people who missed the "start" of the main streams and would prefer to catch up with others instead of only through the recordings.

With regards to pacing & the term "catching up", I'm much more relying on the idea that 1 stream/week vs 2 streams/week will mechanically even out on its own, without needing to push the pace during the streams themselves with that "catching up" mentality.

Of course, if it's already difficult enough for people to find time for 1 stream each week, then trying to catch up by doing several per week just doesn't work out.

[-] ericjmorey@programming.dev 3 points 8 months ago

Your last statement is what I anticipate.

[-] maegul@lemmy.ml 1 points 8 months ago

Awesome to see!

I’ve pinned this if that helps (and you don’t mind).

If you want to put the streams online afterwards (ok if you don’t obviously) I can add the links to the running project post for “Book streams”. Let me know.

[-] Jayjader@jlai.lu 2 points 8 months ago

I'm more than fine with this being pinned, thanks for that.

Similarly, I don't see why the recording(s) shouldn't be included in the project post once they're online. If something happens during a stream that we don't want to preserve, I can always try cutting it from the recording before uploading (or re-uploading afterwards).

I'll try to remember to ping you once I have a public link for the recording.

this post was submitted on 01 Mar 2024
18 points (100.0% liked)

Learning Rust and Lemmy

231 readers
1 users here now

Welcome

A collaborative space for people to work together on learning Rust, learning about the Lemmy code base, discussing whatever confusions or difficulties we're having in these endeavours, and solving problems, including, hopefully, some contributions back to the Lemmy code base.

Rules TL;DR: Be nice, constructive, and focus on learning and working together on understanding Rust and Lemmy.

Running Projects

Policies and Purposes

  1. This is a place to learn and work together.
  2. Questions and curiosity is welcome and encouraged.
  3. This isn't a technical support community. Those with technical knowledge and experienced aren't obliged to help, though such is very welcome. This is closer to a library of study groups than stackoverflow. Though, forming a repository of useful information would be a good side effect.
  4. This isn't an issue tracker for Lemmy (or Rust) or a place for suggestions. Instead, it's where the nature of an issue, what possible solutions might exist and how they could be or were implemented can be discussed, or, where the means by which a particular suggestion could be implemented is discussed.

See also:

Rules

  1. Lemmy.ml rule 2 applies strongly: "Be respectful, even when disagreeing. Everyone should feel welcome" (see Dessalines's post). This is a constructive space.
  2. Don't demean, intimidate or do anything that isn't constructive and encouraging to anyone trying to learn or understand. People should feel free to ask questions, be curious, and fill their gaps knowledge and understanding.
  3. Posts and comments should be (more or less) within scope (on which see Policies and Purposes above).
  4. See the Lemmy Code of Conduct
  5. Where applicable, rules should be interpreted in light of the Policies and Purposes.

Relevant links and Related Communities

Thumbnail and banner generated by ChatGPT.

founded 9 months ago
MODERATORS
maegul@lemmy.ml
sorrybookbroke@sh.itjust.works
Jayjader@jlai.lu