Five for Friday – July 7, 2023

Last week, I scheduled this post, and somehow in doing that I (debatable) made it a private post for subscribers only. That, of course, means that I’m going to schedule this post for 10 minutes from now to see what happens under careful observation.

  • I scheduled the post last week, because I was walking 70 miles of the Pacific Crest Trail. I first walked on the PCT nearly 50 years ago, and have been a bit infatuated with it (off and on) ever since. Someday, I’d like to walk all 2650 miles of it.
  • Open Org recently released their Employee Handbook Template – and it’s kind of cool – or at least worth checking out.
  • I’m currently balancing my DM and Group Chat time between Teams and Slack (weird, but true). I’m pretty sure I don’t want this, but in my haphazard searching to try and see how other folks balance this, I found that some teams just give up and use a tool like Mio Dispatch to make them both feel like one tool.
    I’ll keep looking for a better answer.
  • I think at a lot of companies, it takes too long to get new engineers up to speed. This article on onboarding new engineers hit’s the main points (and with great citations to back up their claims).
  • Finally, some food for thought. This post asks, Are bugs and slow delivery ok? I think the question is valid – and while I agree that for some products, slow and buggy may be ok, but I disagree that it’s 95%…but I sort of hate that the author is sort of right.
    I need to ponder this some more…

That’s all for this week – apologies again for the posting mishap last week, I’ll try to keep my shit together.

Similar Posts

  • Five for Friday – June 11, 2021

    It’s a sort-of-sunny day in the Pacific northwest, and I have the day off from work (which probably means I’m cleaning the garage today. Here are some links to ponder from my recent browser history. Camille Fournier posted a wonderful (and incomplete) list of skills senior engineers need, beyond coding Lisi Hocke wrote a wonderful…

  • What I Do

    When I meet new people, they often ask, “what do you do?” The answer I give initially, and the one I hope to get away with is, “I work at Microsoft.” It rarely works. They inevitably follow up with, “what do you do there?” – which, for better or for worse is a much more…

  • Why Unity?

    A lot of people, both co-workers and not, have asked me why I “chose” Unity for my post-Microsoft career. Although I documented (sort of) why I broke up with Microsoft, and talked in a few other places about my role, I guess I haven’t publicly shared why I’m at Unity (vs any other tech company)….

One Comment

  1. Yes, all posts (also historical) became private.

    I thought you did it to protest the Twitter debacle 😀

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.