Diving back into (Neo)Vim this week for the first time in a few years (have done my core work with VS Code for a while).

Telescope Plugin + Language Server Providers are nice additions to the landscape, and it all feels so powerful, but everything is still so fiddly to setup :/

Really enjoyed these reflections on LLMs: medium.learningbyshipping.com

AI, ChatGPT, and Bing…Oh My

Basically from a “quality triangle” perspective – execs can control costs or time, but holding the line on a minimum quality bar is essentially a core piece of my job, and nobody wins when you try to promise impossible combinations of scope/quality/dates.

In an ideal world, org leaders define goals and teams figure out what to do. But top down asks happen. How I decide whether to push back on top down asks as an EM:

1. It’s fine to be asked for a date or a scope (not both)
2. Never ship something likely to cause an incident

The idea that things become hits mostly due to a small number of large audiences rather than point to point viral sharing seems intuitively correct to me: www.lennysnewsletter.com/p/viralit…

Or at least the large audiences “seed” the viral behavior

As employees return from holiday break, [Shopify] said it’s conducting a “calendar purge,” removing all recurring meetings with more than two people “in perpetuity,” while reupping a rule that no meetings at all can be held on Wednesdays. Big meetings of more than 50 people will get shoehorned into a six-hour window on Thursdays, with a limit of one a week.

This is fascinating to me. I get the desire to remove bloated meetings, but there are recurring meetings that I find genuinely valuable to have sync (project standups / staff meetings). Curious if this ends up being a long term policy for Shopify or more of a culture reset.