Add "how I came to Rust" for review #50
Conversation
|
|
||
| ## Picking up Rust | ||
|
|
||
| I am certainly an early adopter of Rust. I picked it up as a hobby in the early versions, Rust 0.4 was the first version I tried out and around version 0.6, I started writing notable pieces of software in it. That was in 2013. Rust - for me - was the chance to see a language being built. I had no interested in writing a programming language, but I was curious how the process works. I'm still amazsed on how agressively languages can change when compatibilty is no issue. Back then, _all Rust code in existence_ would break _regularly_. |
There was a problem hiding this comment.
amazsed ➡️ amazed
agressively ➡️ aggressively
compatibilty ➡️ compatibility
|
|
||
| # How I came to Rust | ||
|
|
||
| The #rustreach program asked people to write down how they came to Rust and I'm happy to do that. Entering a community or a space is always a moment of orientation process and I hope I can give some insight into that. |
There was a problem hiding this comment.
Hi! As a newbie, I'm not sure what the #rustreach program is... Perhaps some other people might come across the post who are new to it too? Perhaps you could link to a URL for it, and/or add a few words to summarise it? :)
There was a problem hiding this comment.
good point, for background here's the campaign issue: #38
I'll create a separate issue to discuss if the "editorial assistance" tasks should have all the information linked (like this campaign issue) so editors can start editing.
|
|
||
| ## Picking up Rust | ||
|
|
||
| I am certainly an early adopter of Rust. I picked it up as a hobby in the early versions, Rust 0.4 was the first version I tried out and around version 0.6, I started writing notable pieces of software in it. That was in 2013. Rust - for me - was the chance to see a language being built. I had no interested in writing a programming language, but I was curious how the process works. I'm still amazsed on how agressively languages can change when compatibilty is no issue. Back then, _all Rust code in existence_ would break _regularly_. |
There was a problem hiding this comment.
I suggest "no interested" -> "no interest" :)
And "amazsed on" -> "amazed at" :)
|
|
||
| ## Picking up Rust | ||
|
|
||
| I am certainly an early adopter of Rust. I picked it up as a hobby in the early versions, Rust 0.4 was the first version I tried out and around version 0.6, I started writing notable pieces of software in it. That was in 2013. Rust - for me - was the chance to see a language being built. I had no interested in writing a programming language, but I was curious how the process works. I'm still amazsed on how agressively languages can change when compatibilty is no issue. Back then, _all Rust code in existence_ would break _regularly_. |
There was a problem hiding this comment.
Perhaps you could mention where you came to Rust from? Were you a professional programmer at the time? What language(s) were you using before?
| * The openness of the discussion and the ease of participation | ||
| * The air around the community to build something to _use_ | ||
|
|
||
| Rust was always the attempt to apply techniques instead of coming up with their own (obviously, the process means that you need to come up with your own things). It was interesting to watch the process and rare to see that. I enjoyed watching and coding along. |
There was a problem hiding this comment.
I'm not sure I quite understood what this bit means about "applying techniques instead of coming up with their own"? Is it talking about the designers of the language? I thought from the earlier paragraph that it might be more like the opposite: because it is a new language, like an open book, it would be possible to come up with new suggestions rather than having to use existing techniques? Perhaps clarifying this slightly or adding an example might help?
|
|
||
| ## Rust Berlin | ||
|
|
||
| In 2014, I got in touch with @johannh about running a meetup. We were both curious about Rust, but wanted to get in touch with other people who were interested. So we formed Rust Berlin and quickly thereafter the Rust Hack & Learn, where - instead of coming and listening to a talk - you could pass by and hack on your own project. The Hack & Learn is still running every other week. |
There was a problem hiding this comment.
Perhaps you could make "Rust Hack & Learn" link to a website if it has a specific one?
There was a problem hiding this comment.
Ah same comment with RustFest below :)
| * Rust has working complaint structures. If I have a problem with how things are going, I know where to send them. I know someone will reply with appropriate urgency. (A week or so, we are hobbyists) | ||
| * Issues, especially social ones, will be dealt with. At some point, obviously, but we work on things. I like the way the project is improving at a steady pace and not rushing things. | ||
| * Actively working for a good tone and balance. Rust has people of many cultures and communication issues arise from that. I don't want to make that sound like I'm the master of this, I have been called out multiple times for ways of arguing or tone. This is great, it starts a conversation and allows to check behaviour. | ||
| * No "you must be this tall to be a project member". If you want to start working on something of project capacity, let us know! |
There was a problem hiding this comment.
I'm not sure what "something of project capacity" means, perhaps it means "something on the project, in any capacity"?
| * No "you must be this tall to be a project member". If you want to start working on something of project capacity, let us know! | ||
| * We appreciate that people have lives outside of the project. You can only spend 4 hours a month? Cool, let's make sure they count! | ||
|
|
||
| A friend once told me that I see problem everywhere. And she's right. But a stated problem is something you can work on. The Rust project, over the last years, has found a good working scheme in which problems are stated, inspected and subsequently fixed. I like that. And for me personally, that means my problems are taken seriously. My part of the trade is that I take all of the other problems with seriousness and allow them to have room. |
There was a problem hiding this comment.
"I see problem everywhere" -> "I see problems everywhere" :)
|
|
||
| ## Why I'm staying | ||
|
|
||
| I guess you won't be able to draw that much from that story. All the conditions might not apply to you. So I guess it's important to tell you why I am still around. And that's because I think the Rust project gets a lot of things _right_. Some of these things weren't always right and there's always things that need to be fixed. A previous draft of this text had included some of the things that were broken. I decided to remove them, because they are _fixed_. For me, Rust - the project - is based on a couple of things: |
There was a problem hiding this comment.
This is a style comment which is somewhat individual / personal preference, so please feel free to stick with your preferred style! But if you like, I think that you do not need to be apologetic here :)* I think you could perhaps reduce the first couple of sentences down to something like "Your path into Rust might be different to mine, but next I'd like to tell you why I am still around..." ?
*It has also been my tendency previously to apologise / try to reduce expectations a bit upfront (for example at the start of a talk to say "This might not apply to all of you...", "I'm not an expert on this..." etc). But I have heard good advice from others that it is better to avoid doing that, and be a bit more positive/bold! :)
| The #rustreach program asked people to write down how they came to Rust and I'm happy to do that. Entering a community or a space is always a moment of orientation process and I hope I can give some insight into that. | ||
|
|
||
| My path is highly individual, but yours will be, too. Own that. It's great. | ||
|
|
There was a problem hiding this comment.
Might you have an image or two that you could include? In my experience, including at least one photo/visual in a blog posts can really help! It gives a visual hook when the post is shared on social media, for example, and just helps make it look more appealing in general. Perhaps a photo of you at one of your earlier Rust events, for example?
There was a problem hiding this comment.
I find visuals distracting, so I avoid them on my web spaces, too. We also have no pictures of the Hack & Learn.
|
|
||
| I would still like to encourage you to check us out a little. While there's no "formal" way to join most of the teams, it's mostly easy: show up and be willing to work on tasks. Or, even better, if you have a subject that is not covered by any of the groups, form one! It isn't even _as_ huge of an amount of work as you may think. | ||
|
|
||
| The barriers are much lower then you might think and tasks are aplenty! |
There was a problem hiding this comment.
Great post! I hope I didn't put you off too much with my comments above. It looks very good to me. Cheers!
|
@poshaughnessy I acted on most of you feedback and pushed a new version. |
|
Thanks, @skade That looks amazing. We look forward to more people coming up with their blog posts! 🎁 |
This is for the #rustreach campaign