Culture & Workflow
Daily Checklist

Daily Developer Checklist

This checklist outlines the daily responsibilities for all developers at Pivot. These tasks should be completed each workday to maintain code quality, team communication, and system reliability.

Morning Routine

1. Share Planned Deliverables

At the start of your workday, share your planned deliverables for the day in the #engineering Slack channel. This helps the team stay aligned on what everyone is working on and enables better collaboration.

What to include:

  • Key tasks or features you plan to work on
  • Any blockers or dependencies you're aware of
  • Estimated completion times for major items (if applicable)

Example:

Today I'm planning to:
- Complete the user profile API endpoint (PR ready by EOD)
- Review the authentication refactor PR
- Debug the WebSocket connection issue in pilot service

2. Address Urgent Issues

Check for any issues marked as Urgent and address them first thing. Urgent issues should never remain stuck in the urgent state - they require immediate attention and resolution.

Where to check:

  • Linear tickets marked as "Urgent" priority
  • Slack notifications in #engineering or #monitoring channels
  • If you're on-call, you'll be paged via Rootly for urgent production issues

Important: If you cannot resolve an urgent issue yourself, immediately escalate it to the team or relevant domain expert. Don't let urgent issues sit unaddressed.

3. Check Sentry for New or Rising Issues

Review Sentry for any new errors or issues that are trending upward. This proactive monitoring helps catch problems before they impact users significantly.

Action items:

  • Create Linear tickets for new issues that need investigation
  • Update existing tickets with new information
  • If critical, address immediately or escalate to the team

Sentry links:

  • Production: [Check your Sentry dashboard]
  • Staging: [Check your Sentry dashboard]

4. Review Pull Requests

Check for open pull requests that need your review. Timely PR reviews are critical for maintaining development velocity and ensuring code quality.

Review priorities:

  1. PRs explicitly requesting your review
  2. PRs in your area of expertise
  3. PRs that have been waiting longest for review

Review guidelines:

  • Aim to complete reviews within 24 hours of being requested
  • If you cannot review promptly, decline the review request so the author can find another reviewer
  • Follow the Code Review guidelines when reviewing

GitHub PR links:

Throughout the Day

  • Keep the #engineering channel updated on significant progress or blockers
  • Continue monitoring Sentry for new issues
  • Respond to PR review requests promptly
  • Update Linear tickets as you make progress

End of Day

  • Update your Linear tickets with current status
  • If you didn't complete planned deliverables, communicate why in #engineering
  • Ensure any work in progress is committed and pushed to your branch
  • If you're blocked on something, communicate it so others can help unblock you tomorrow

Why This Matters

These daily practices ensure that:

  • The team has visibility into everyone's work
  • Critical issues are caught and addressed quickly
  • Code reviews don't become bottlenecks
  • We maintain high code quality and system reliability
  • Communication remains transparent and proactive
Getting StartedCode Review