Blogging about programming is tough. I often forget who that I am writing for and why. Eventually, I come back to the comfortable feeling and attitude that this blog is principally for myself, and myself only.

A friend from Recurse Center suggested to me that I start a dev diary while I work and grow as a nascent developer. It was a great idea, but I wasn’t sure what to write about. Should I do stuff about Ember.js, since that’s what I do most of my time at work? Or about Ruby, my first programming language?

Neither of these felt right. I want something fresh, something bizarre and incredibly difficult to learn. Something that has no immediate benefit that wouldn’t cloud my good intentions, but would at least expose me to some principles of computer science that I didn’t learn while earning my B.A. in Comparative Religions.

Rust was it. It has all the wrong (right) things for me.

  1. Statically typed
  2. Strong Concurrency (My only exposure to concurrency was through experimenting with Ruby threads)
  3. Scary systems programming language
  4. No run-time environment (REPLs have been my primary vehicle for learning)

So I may not get to 100 days - let alone straight - of writing about my experiences in learning Rust but I’m really looking forward to the challenge.

fn main() {
    println!("Hello, World!")

let’s do this