Check our website for properly formatted versions of these documents.
We are a number of groups of hackers in the UK and abroad learning and improving in the use of the Rust programming language.
We've got a Github organization where we can store common
materials/results, and the IRC channel #rustaceans.uk
on
irc.mozilla.org
We're currently 3 groups, which have their own area on this website:
See past shared events and the past events pages of the individual groups: London, Cambridge, Rome
We are doing the following in parallel sub-groups:
-
Get a minimal fluency in Rust, by working through the Rust book (online), or other ideas:
- rustlings (learning Rust through snippets)
- go through the Advent of Code and implement it in Rust
- exercism.io
- hackerrank.com
- RustConf 2017 Tutorial Exercises
Keep in mind that this is not a course, but a co-learning experience. You'll group up with other people (about 2-5 each) to work through the material; if your group is stuck, ask the other groups or see whether you can get tips from Rustaceans working on projects, or via the IRC channel, or ask the organizers for help.
-
Working on projects: in pairs, teams, or alone; even if you're working alone, you may find it beneficial to have other Rustaceans around. You can also ask questions on the IRC channel, or ask us to ask the question to the plenum.
See the lists of projects (London, Rome).
Also check project ideas. If you stumble on an interesting project please add it there even if you don't intend to work on it yourself during the evenings.
At each event we'll first give a quick overview on what's going on so that new attendants can decide which sub-group to join. Also, after the event we'll add a summary about the status of each sub-group to the wiki here.
Some ideas we might pick up if deemed useful:
-
Help/tutoring: we can try to enable people with a question that deserves answering by an (intermediate) expert, or discussion by the group, to come forward and find such an expert or set up a discussion. E.g. (fictional example) someone finds there are mysteries around interactive debugging of Rust programs, come forward ask whether anyone is around who feels up to answering the questions or give a tutorial, if there is nobody, we could try to find someone who researches the topic for another time and will then present it.
-
Code Dojo (which means, decide at the start of the evening what to figure out or write, elect someone to type at a common screen, everybody pitches in with steps helping to solve it). We could do these at some regular Rust user group meetings in the classroom instead, though.