Current reading: the New Yorker on what cannabis legalization has done to growers in Humboldt County: newyorker.com/news/dispatch/ho

I didn't use to care about this topic...

Take me back to the parakeet city
Where the birds are green
and their tails are pretty
Oh won't you please take me home

RT @briantylercohen@twitter.com
Jeff Daniels is so, so on point. Watch every second of this.

@NicolleDWallace@twitter.com responds perfectly at the end: "Wow."

I just ate a chocolate chip cookie and my mood is now good, albeit briefly before the sugar crash happens.

I installed a cli interface to gcal and I can't believe I didn't do this years ago.

The SRE mindset is a new thing for this company, but it's happening.

eaze.com/careers

We're rebuilding with modern tools and a modern mindset. If you want to have an impact, we've got opportunities at every level of the stack, from infra on up to the website.

eaze.com/careers

The company I work for is hiring. We're rebuilding our tech stack for the future: legal cannabis delivery in all 50 states is gonna happen & this company is poised to do it.

eaze.com/careers

Anyway, I had no point other than that when I need to make something fast I don't reach for Javascript, but when I need to be fast about making it, I do. But my mileage is beginning to vary.

The barrier to entry for JS is ever-rising. This makes me sad.

Downsides: I have now patiently unknotted enough async confusion & loop misery that I begin to suspect the language of now being in its own way. Or maybe a better way of putting it would be that people have to re-learn JS.

Additional benefits of the js tradeoff: huge amounts of existing code written for you in the node package manager.

If you really cared about perf you’d write it in something other than JavaScript.

Show more
Life raft.

Ceejbot's mastodon instance. This is an overprovisioned, personally-run instance running on AWS. I welcome friends to create accounts here. I intend to run it as long as people are using it.