This fortnight's newsletter has a lot of really good content in it https://t.co/RGv0BEo1co
(big thanks to @StokesXandra for pointing out the broken link on the org structure post in the email, now fixed on web)
New features this week https://t.co/vaJSfzcA87
Super helpful for teams that need to work within a monorepo or monitor activity for certain filetypes across an entire GitHub org (like security or frontend)
This week we interviewed @siddhantgoel, founder of @devtomanager about his experiences interviewing so many technical leaders about their promotion https://t.co/bjKo3CAVXz
Need to know what's going on in your engineering team but falling behind because there's just too much going on?
Try https://t.co/krxT7aA0GL with a free 7 day trial
One of the useful concepts (esp for one tech lead amongst many) is carving up org pull requests into these four categories. Each kind needs different attention.
I did want to name the last one not_my_circus_not_my_monkeys? but it was a bit long.
Today’s the day our newsletter goes out so make sure you’re subscribed at https://t.co/W4ezp9J3VB
It could be a doozy. Who knows? Not me because I haven’t written it yet! But it could be and isn’t that exciting?
Shared a few of the decisions that went into building and hosting the @HecateApp MVP over on @stackshareio https://t.co/I5vQkBiXe2 if anyone's curious.
@darthted ha! another book that would go in the 6-10 follow up recommendations is The Halo Effect, which devotes a significant number of pages to tearing that one to pieces