cross-posted from: https://sh.itjust.works/post/13993219

The concept

A streamed reading club focused on rusts The Book and becoming reasonably good rust developers through community collaboration. If you’re interested, please comment so we know this’s something you’d like to join in on.

A Begining

To begin, I’ll be setting up a twitch stream where we read through the book together and solve some problems together related to the concepts provided. We’ll be able to collaborate in chat, and talk about it here after each stream. This way, we’ll be able to lean on each other or just hang out while we learn the language Lemmy uses for it’s backend. Other hosts will be welcome as the end goal is to create a group of people whose goal is to support our collective growth as developers

Anybodies welcome of any skill set, whether or not they want to continue on once we get to lemmys code base. If you’re completely new to rust this is a great place to start and if you already know the language we’d love to have you all the more. At the very least it’s a good networking opportunity but you’ll likely learn more than you thought.

Timing

Please comment your availability so we can find the best time and day to do this. As a stand-in and default though, 6:30pm EST (New York Time) on tuesday will be the start time. I’d be available on most days myself after 5pm Eastern Time (new york) though so don’t hesitate to suggest another time/date.

Where?

For now, I’ll be streaming this on a twitch channel I created a bit ago but never used. The link is here: https://www.twitch.tv/deerfromsmoke

Thank you @morrowind@lemmy.ml for the idea.

3 points

Oh hey, thanks for cross-posting. I was just about to do this but luckily while editing the title it showed these. Appreciate you saving me the effort, and I’m excited to see you all tomorrow

permalink
report
reply

Learn Programming

!learn_programming@programming.dev

Create post

Posting Etiquette

  1. Ask the main part of your question in the title. This should be concise but informative.

  2. Provide everything up front. Don’t make people fish for more details in the comments. Provide background information and examples.

  3. Be present for follow up questions. Don’t ask for help and run away. Stick around to answer questions and provide more details.

  4. Ask about the problem you’re trying to solve. Don’t focus too much on debugging your exact solution, as you may be going down the wrong path. Include as much information as you can about what you ultimately are trying to achieve. See more on this here: https://xyproblem.info/

Icon base by Delapouite under CC BY 3.0 with modifications to add a gradient

Community stats

  • 2

    Monthly active users

  • 102

    Posts

  • 481

    Comments