Mark Larah

(There are legit reasons why you might still want to do this, such as custom error classes for control flow, but this example above is not it)

Can’t unhear: every door on TV is the nosiest, heaviest door ever

I find myself linking to stuff a lot in PR comments so I can avoid typing out the same explanation of stuff when it pops up a lot

And if there isn't, it's a good opportunity for you to publish such a page :)

when reviewing PRs, if commenting on a general point (e.g. "can we use a more specific type than `foo: Object`"), see if there's a source of truth (e.g. eslint docs) or some other authoritative literature (e.g. http://c2.com ) on the subject explaining why and link to it

Love it when American stores have “savings events” - i imagine these are very formal occasions? What’s the dress code? Do I have to show my 20% off coupon invitation email to the security guard at the door?

What idiot called them dental records and not tooth factor authentication

tl;dr Ultimately, there’s no points for going fast and crunching through all the newhire tickets. Usually, we want the opposite. Those first few weeks are roped off explicitly to go slow and to take time to learn as much as possible - and not ship stuff blindly.

I usually say something like “Editing a file in a directory? Maybe also sneak a peek at some sibling files, or trace where some interesting looking helper functions come from! Go find the docs where available. If you think the ticket should only take a day, take two.”

Mentoring a new hire? Give them the space and time to be curious and explore the codebase, beyond just what the ticket says. The point of “fix whitespace bug” on homepage isn’t just to delete a newline as fast as possible. 1/?

does anyone have a gmail invite

Million dollar idea: Dr. Brown’s x LaCroix @drbrownsbaby @lacroixwater I’ll take 3% ty