Înapoi la articole →

Cel mai recent articol

Ultima verificare

Urmăritori 0 urmăritori
Articole: 132
  1. Incident Report Template

    PreviewMarkdown Incident Report: Lead Empty Analysis Date Empty Severity Empty Treatment Ticket Empty ⚠️ **Guidelines for Incident Reports** Fast and light: Keep the report concise, ≤ 500 words, less than an hour of your time.

  2. Friction Log Template

    PreviewMarkdown Friction Logging: TEMPLATE Author: Date: Size: S | M | L What is a Friction Log?

  3. PreviewMarkdown Bug and Incident Severity Guide Principles Fast triage: We grade and prioritise the bug straight away.

  4. 2023 In Review

    2023 was an incredible year in our industry, so I thought I’d look back and share the things I’ve loved reading, watching, learning and doing this year.

  5. Caitlin Sadowski, Emma Söderberg, Luke Church, Michal Sipko, Alberto Bacchelli | 2018 | Paper Benchmarks for Code Review It’s handy as we talk about code review to use some benchmarks that anchor our expectations for review performance in data.

  6. What Great Looks Like

    PreviewMarkdown What Great Looks Like: NAME - TITLE ⚠️ This is a work in progress, the steps to get this live are: (1) writes a first draft from this template, (2) we review it together in a 1:1 (3) we re-draft based on feedback (4) we share it with the o…

  7. Nicole Forsgren, Margaret-Anne Storey, Chandra Maddila, Thomas Zimmermann, Brian Houck, Jenna Butler | 2021 | Paper Summary I read the devex paper by a few of the same team recently so I went back and read the orignal SPACE paper as well.

  8. Abi Noda, Margaret-Anne Storey, Nicole Forsgren, Michaela Greiler | 2023 | Paper Summary Devloper Experience or DX focuses on the lived experience of developers and the points of friction they encounter in their everyday work.

  9. Hiring Product Managers for Deep Tech I was catching up with a peer earlier this week and towards the end of our call, they threw out an interesting question - if you were hiring a product manager (PM) for our team right now, what profile would you hire?

  10. A skill that a lot of engineers develop as they move towards a Senior level is the ability to make quick technical decisions verbally or in short form (say, a Slack post).

  11. High Output Management

    Andy Grove’s masterpiece on management and leadership was a book I reached for as I transitioned from a role as a senior IC to leading an engineering organisation for the first time.

  12. About

    I lead technology at Hofy - a Series B startup revolutioning how we equip the world’s talent.

  13. Copyleft Licenses

    License Checking I’ve been through a couple of due diligence processes now (sales, funding rounds), and one question that always gets asked is whether we have any dependencies with a copyleft (viral) license in our codebases.

  14. 1:1 Template

    PreviewMarkdown XX <> TH Important Links Kick Off 1:1 Brag Document ⏫ Growth Tracker Growth We should be catching up on your growth every four weeks, our last growth chat was: Never!

  15. PreviewMarkdown TDD Template How to use this document (remove once read) Use it as a checklist to make sure you cover all bases, remove anything you don’t need.

  16. Decision Document

    PreviewMarkdown Decision Template Maximum 1500 words.

  17. VS Code

    I’ve done a lot of technical hiring and a part of that process has always been a hands on paired programming exercise.

  18. Company Strategy

    PreviewMarkdown Strategy Template What is strategy?

  19. Superforecasting

    In work (and life) we’re making (and receiving) predictions all the time - from when that all important project is going to ship to how a core business metric is going to move over the next few weeks via how long it might take to hire that critical role.

  20. Multipliers

    Multipliers are leaders who amplify the intelligence and capabilities of their teams.

  21. Flow

    Mihaly Csikszentmihalyi’s book “Flow” explores the concept of flow, a state of optimal human experience where individuals are fully immersed and highly focused on an activity.

  22. Regex

    Early in my career watching other engineers pattern match across a codebase or some logs using regex felt like some kind of inaccessible, dark magic - they could find (and replace) what they were looking ten times faster than I could.

  23. Oh-My-Zsh

    Oh-my-zsh is another little bit of engineering secret sauce, though if you’re fresh to using the framework I’d probably carefully review alternatives and find something that closely fits your workflow before diving in.

  24. Bash

    Getting some ’nix super powers is part of the secret sauce that most high performing engineers have, and this deck can help bootstrap that process, fill in gaps or retain muscle memory if you’re spending less time in the terminal than you used to.

  25. Getting Things Done

    Getting things done is so ubiquitous that it probably needs no introduction, but as my career developed and my home life grew more complex I needed to improve how I managed my time and that meant leaving behind some bad habits.

  26. Security Review

    PreviewMarkdown Security Review Checklist (TEMPLATE) Completed By: @yourself Date: **@Today** You should be able to find out the majority of the answers to these questions by browsing the vendor’s website.

  27. PreviewMarkdown PRD: [PRD TEMPLATE] How to use this document Use it as a checklist to make sure you cover all bases, remove anything you don’t need.

  28. Git

    Helps with memorising git commands and flags to get you going a bit faster in the terminal.

  29. Kick Off 1:1

    PreviewMarkdown Kick Off 1:1 This document is intended to be a first step together where we contract to understand what you need to get the most out of our 1:1 conversations.

  30. Brag Document

    PreviewMarkdown Brag Document For a bit of background, Julia Evans has a nice write up on brag documents here.

  31. Peak

    Anders Ericsson’s masterpiece on how to acquire expertise through deliberate practice changed the way I approached learning - for example, by making my approach far more systematic and methodical.

  32. How to take smart notes

    Sönke Ahrens | 2017 | Amazon | Goodreads Why take notes?