Takes
*Conflict of interest: I am married to Becky and therefore predisposed to judging it more harshly https://gram.betterwithbecky.com/podcasts/9
]]>*Conflict of interest: I am married to Becky and therefore predisposed to judging it more harshly https://gram.betterwithbecky.com/podcasts/9
]]>*Conflict of interest: I am married to Becky and therefore predisposed to judging it more harshly gram.betterwithbecky.com/podcasts/9
]]>*Conflict of interest: I am married to Becky and therefore predisposed to judging it more harshly https://gram.betterwithbecky.com/podcasts/9
Regardless, the blog was busy since we last checked in:
Also since I last wrote you, they held the final RailsConf, an event and community that had a huge impact on my career. I was honored that Aji Slater summarized my 2017 keynote on stage, even though I don't own a single pair of white pants:
npm
or uv
install path alongside a brew
one, I choose brew every single time.
And yet, when it comes time to publish a CLI of my own, I usually just ship it as a Ruby gem or an npm package, because I had (and have!) no fucking clue how Homebrew works. I'm not enough of a neckbeard to peer behind the curtain as soon as root directories like /usr
and /opt
are involved, so I never bothered before today.
Some links you won't click:
*Conflict of interest: I am married to Becky and therefore predisposed to judging it more harshly gram.betterwithbecky.com/podcasts/9
]]>*Conflict of interest: I am married to Becky and therefore predisposed to judging it more harshly https://gram.betterwithbecky.com/podcasts/9