Patrick writes about Did.txt
Time flies by when you’re learning how to code. Its super important to take a second every once in a while to simple write down what you did during the past mental sprint. Writing down what you learned solidifies the knowledge.
This is not a million miles away from what we do internally, where we have a concept of 'snippets'. It's up to you how you manage it, but it's a great way of keeping track of what you did, but also shared across your team you get a nice picture of what your peers, managers and reports are also doing.
The model I like is to split each weekly summary into a 'what I did' and 'what intend to do this week'. It helps me reflect and plan at the same time.
I lead the Chrome Developer Relations team at Google.
We want people to have the best experience possible on the web without having to install a native app or produce content in a walled garden.
Our team tries to make it easier for developers to build on the web by supporting every Chrome release, creating great content to support developers on web.dev, contributing to MDN, helping to improve browser compatibility, and some of the best developer tools like Lighthouse, Workbox, Squoosh to name just a few.
I'm trialing a newsletter, you can subscribe below (thank you!)