A half-hour to learn rust →

A half-hour to learn rust got a lot of buzz on hackernews. I’ve been meaning to take a closer look at Rust. The issue is that its syntax varies from any other programming language I’ve used, so it is a little overwhelming. I’m going to take a moment to look over this post to get a better understanding of the syntax.

Qualitative and Quantitative Data in Conversation

A speaker can sometimes prioritize the wrong details in a conversation. When a speaker glosses over the essentials, it’s much harder for the listener to reason about what isn’t essential.

Andrew has booked a hotel room, but realizes he underestimated how long he would need to stay. He calls the hotel and longwindedly explains where he’s coming from, why he’s going there, even the month he’s staying, and that he has booked the wrong dates. The listener at the hotel front desk is confused about what Andrew needs, so asks what he needs. Andrew is frustrated because he just explained what he needs! He needs an earlier check in date.

Andrew isn’t communicating the quantitative data very clearly. He is caught up in a narrative.

Starting off on the right foot

Andrew is better suited by letting the listener know outright who he is and his relationship to whom he is calling. This is a common problem in both business-to-business interactions and business-to-customer interactions. The speaker starts with a story before they give the story context.

Andrew should be ready to spell his last name. An interruption asking for his last name shouldn’t startle him. He can then tell the listener the dates he has booked and what changes need to be made. It’s even okay to add a little narrative here so long as Andrew focuses on effectively communicating the quantitative information.

Andrew benefits from getting through the conversation faster having effectively communicated his needs.

Why does it matter?

It doesn’t matter to people who don’t care about being polite or communicating clearly. Andrew can carry on bloviating about the qualitative while glossing over the quantitative and do just fine.

For those wanting to be understood: focus on clarifying the data and then tell a story. Listeners will appreciate it.

I started going on night walks again. I had a sort of reluctance up until now because I was worried I wouldn’t be able to enjoy the darkness like I had in my teens. I was exhilarated when I realized the moonlight still lit up the vegetation like it had when I was younger.


I have put the minimum effort into an _s theme for this site. It has virtually no styling at all and I really like that. I think blogs in general have gotten too commercialized. The themes offered on the WordPress themes site are optimized for making sites that look “big”. A big site, after all, gives the impression of competence.

I don’t want a big site. I want to start small and make methodical changes. That might mean no changes at all. I just want to focus on writing how I feel and sharing interesting snippets from the web. I’m not here to impress anyone.

If you are interested in reading what I have to say, I would like to know. I would love to read other people’s blogs. I have kind of lost touch with this part of the internet — the blogosphere. The social media before the word social media was popularized. There is something so tiresome about using Twitter, Facebook, Instagram, et al. I don’t know if it’s the way that content seems to take the same shape and format on each platform, the attitudes people have on them, or maybe I just don’t fit in well on these platforms. Let’s not forget how annoying it is when people write “essays” on Twitter. Just use a damn blog!

So here I am. I’m going to try to stick with it.