- Review all your work from an outcome perspective. When reviewing and getting reviewed, always ask, “To remind you, the goal here was __, and the key hypothesis is/was that ___.”
- Strategy is all about figuring out how we will win. It is where we specify the most critical long-term challenges facing the company and the rocks that are the most important things, not to win the battles today but to determine how we will have won the war three years from now, how we will achieve our vision, and how we will win.
- The market matters more than the team. Problem more than solution. Question more than answer. Network more than selection. Set up more than execution. (Jack Altman)
- The prompt reply to an email / text / DM is the biggest sign of competence in any role. Even a “will read and get back soon” acknowledgement will go a long way.
- To get a small idea of the world around you, try taking a moment to imagine what each food you eat might taste like based on its colour, texture, and other characteristics. Then, take a non-food object in your environment and define its characteristics. What is its colour, shape, and size? Which other foods can you think of that share those characteristics? For example, if the object is a wooden cutting board, it might be the colour of butterscotch or caramel and have a similar shape to the soft rectangles of chewy candy. Is the surface hard and smooth, like a table, or is it soft and warm, like a fleece jacket? Is it warm or cool to the touch? The texture of the wood can help us imagine if we associate it with a hard caramel candy, a soft and chewy one, or something warm, like caramel sauce. What it’s like to be a food writer when you can taste everything you see @darin @abhishek @elliot
- Figma does eng crits to engineer feedback for all technology solutions they build. They use it to get feedback early, not seek approval. They use crits to brainstorm ideas, identify challenges, validate hypotheses, share knowledge and call out irreversible decisions.
- Software Development isn’t just about writing code but modelling complexity. Engineers should effectively manage the complexity and translate the business problems from real-world domains to digital models. Thoughts on the Future of Software Development @darin @abhishek @elliot.
- An engineering team should be skilled in technology and have strong opinions about its impact on people’s lives. They must strive to become experts in these issues by studying relevant publications and learning from scholars and practitioners. Building engineering @darin @abhishek @elliot
- A list of things that don’t work
- The web bloat impacts users with slow devices.
What I’ve been reading (W13, 2024)
On strategy, taste, and engineering processes/craft