David Hanson

David Hanson

Design and Engineering

Purpose: Build the software the world needs to unleash evolution and empower purpose in organizations

  • Architect

    for frontend

    Purpose:

    Sustainable, healthy architecture for the long run

    Accountabilities:

    • Planning and executing large infrastructure investments and improvements.
    • Reviewing PRs and providing feedback to Developers on request
    • Providing feedback on suitability of developer-initiated infra stories
    • Blocking or escalating work on any developer-initiated infra stories that seem harmful or overly wasteful
    • Providing ad-hoc technical leadership as opportunities present themselves
    • Integrating objections from @Product Vision to potential investments for improving development capacity, before committing to those investments
    • Supporting @Developer in using defined source control systems effectively and efficiently
    • Soliciting and integrating feedback from other @Architect role fillers on design and execution of large infrastructure changes
    • Maintaining and prioritizing the issues in the Linear Infra Work project
    • Publishing architectural guidelines for @Developer to follow
    • Reviewing pull-requests for adherence to architectural guidelines

  • Developer

    Purpose:

    Satisfy the customer through early and continuous delivery of truly valuable software

    Accountabilities:

    • Participating in team processes defined by @Agilator
    • Following architectural guidelines published by @Architect
    • Attempting to reproduce bugs at the request of @QA
    • Implementing GlassFrog user stories, bug fixes, and chores to improve the product and GlassFrog operations
    • Adding infra stories to get rid of dead code as observed
    • Sharing development challenges with other @Developer role fillers as challenges arise in their development work
    • Delivering bugs and stories in a testable state before triggering @QA to test them

  • Developer Onboarding & Offboarding

    Purpose:

    Incoming developers are up and running, outgoing developers are disconnected

    Accountabilities:

    • Creating a checklist of onboarding activities for new developers within the circle
    • Creating a checklist of offboarding activities for developers leaving the organization
    • Ushering new developers through the onboarding checklist
    • Coordinating the disconnection of outgoing developers according to the offboarding checklist

  • Eye of the Frog

    for one-off reports

    Purpose:

    Internal stakeholders have visibility into GlassFrog usage and subscription data

    Accountabilities:

    • Cataloguing and publishing all existing sources of GlassFrog usage analytics data with links to the raw data
    • Processing relevant raw analytics data into an easy to consume and useful format
    • Publishing easy-to-consume and useful usage data internally
    • Analyzing data to inform product design
    • Collaborating with Marketing to create better usage insights

  • Performance Champion

    Purpose:

    GlassFrog is fast, so very fast

    Accountabilities:

    • Identifying ways to measure the customer's experience of GlassFrog performance and availability
    • Requesting the creation of specific monitors from relevant roles
    • Alerting appropriate processes and roles when GlassFrog is not operating within desired thresholds and identifying acceptable thresholds for performance and availability
    • Reporting on GF performance and availability monitoring
    • Monitoring GlassFrog for performance issues and triaging them into projects for the appropriate roles

  • System Monitor

    Purpose:

    Unspecified

    Accountabilities:

    • Monitoring application performance, and triaging or submitting critical bugs for significant performance regressions or problems
    • Observing the logs for errors frequently, preferably every day, and alert the team if something got worse

Accessibility champion

Purpose: Unspecified

  • Circle Lead

    Purpose:

    The Circle Lead holds the Purpose of the overall Circle.

    Accountabilities:

    • There are no accountabilities defined for this role.

Developer

Purpose: Satisfy the customer through early and continuous delivery of truly valuable software

  • Circle Lead

    Purpose:

    Satisfy the customer through early and continuous delivery of truly valuable software

    Accountabilities:

    • There are no accountabilities defined for this role.