<story><title>Yes, I am still learning Rust</title><url>https://llogiq.github.io/2020/03/07/learning.html</url></story><parent_chain></parent_chain><comment><author>brundolf</author><text>I used to put every technology I had any experience with on my resume.&lt;p&gt;Then I started only listing the ones I knew the best.&lt;p&gt;Now what I do is treat the list as aspirational. &amp;quot;Here are the technologies that I&amp;#x27;d like to work with (and which I&amp;#x27;m familiar enough with that I could figure the rest out on a job).&amp;quot; I try to paint a story with those technologies: this combination of technologies draws an outline around the type of work I want to be doing.&lt;p&gt;I did this recently with Rust on the list even though I&amp;#x27;ve only done a couple of personal projects with it, and the presence of it specifically made me stand out to a company that I&amp;#x27;ll soon be starting a position at! They use Rust and are sort of a dream job in a couple other ways too. They said the presence of that language spoke to the personality of the developer, and the kind of things he was likely interested in.&lt;p&gt;Takeaways: don&amp;#x27;t undersell yourself, and tell a coherent story.&lt;p&gt;Edit: To be clear, I was not being deceptive. Through the interview process the company learned precisely how well I know the things that I listed - we even dove into some of my projects together - and they were still excited to hire me. My point is that &amp;quot;knowing general principles&amp;quot; + &amp;quot;being fairly comfortable in a particular language&amp;quot; is often all that&amp;#x27;s really being asked for, and doesn&amp;#x27;t need to be disqualified with &amp;quot;still learning&amp;quot; just because you don&amp;#x27;t know everything there is to know.</text></comment>
<story><title>Yes, I am still learning Rust</title><url>https://llogiq.github.io/2020/03/07/learning.html</url></story><parent_chain></parent_chain><comment><author>klodolph</author><text>I’m still learning Rust, but I’m developing a deeper appreciation for Go. I’ve already &lt;i&gt;learned&lt;/i&gt; Go. As far as I can tell, I’m a Go expert.&lt;p&gt;Rust has a pretty large surface area. There’s a ton of places where you can get overwhelmed by choices. For example, when you’re working with slices, you might find yourself thinking about the pros and cons of different approaches using indexes, convenience functions, pattern matching, or iterators.&lt;p&gt;It’s a big toolbox, and sometimes I wish I had a smaller toolbox, even if it means giving up the choice of which tools to keep.&lt;p&gt;So, I’ll still be learning Rust for a while, too.</text></comment>