Greghaus

Advanced Triage Skills for quicker resolution.

Greghaus helps the on-call engineer move from incoming issue to useful context quickly, with a workflow built around triage instead of generic dashboards.

Who is Greghaus for?

Greghaus is built for the GREG — the Generally Responsible Engineering Guardian — the rotating weekly role at Readwise where one engineer steps up to keep everything running smoothly.

You won't get much done in the way of regular tasks this week, so don't feel bad about it. You are helping the team immensely by taking the load of immediate problems off of their mind.

Core responsibilities, in priority order

  1. 1.

    Urgent bug triage

    Own bugs that are urgent and important. Fix them yourself or pair with the right developer. It's still your responsibility to ensure it gets fixed.

  2. 2.

    Sentry error monitoring

    Periodically check incoming errors. Critical ones get pinged to the responsible dev (use git blame). Others get a Linear ticket filed. Merge duplicate Sentry issues. Archive one-off errors or errors already being worked on.

  3. 3.

    Fix one spammy error

    Pick one noisy error and fix it during your GREG week.

  4. 4.

    Answer #dev-questions

    Best effort to answer yourself; if you don't know, ping someone who does. Don't leave questions unanswered for more than 2 hours.

  5. 5.

    Monitor dashboards

    Render (website status), NewRelic (task queues), PgHero (DB), integrations dashboard. Sound the alarm in #dev if something looks off.

  6. 6.

    Review PRs

    Be more active than usual reviewing pull requests to unblock developers.

  7. 7.

    Dev experience

    Work on your favorite devexp task: dependency upgrades, dependabot PR maintenance, local dev improvements.