Andrew Tabb Get in touch

Andrew Tabb

Self-taught software builder · Raleigh, NC

I build and run my own web and game products.

Pendo, hands-on

Hands-on with Pendo

I learned Pendo by using it. Here is what I have done so far.

1

Instrumented a live app with Pendo. Stood up a four-page web app ("Acme Tasks"), installed the Pendo agent, verified with pendo.validateInstall(), tagged four pages and five features, and built a segment and an Add Task → Done funnel.

2

Used Novus end to end. Connected Novus to a scoped repo, reviewed and merged its SDK-install pull request, and built a product map. Novus is built on Anthropic's Claude, which I work in daily.

3

Pendo Academy in progress. Product Analytics and Digital Adoption tracks, working toward the Pendo Admin Certification.

Add Task → Done funnel (built in Pendo)
Visit app
Add Task
Task added
Done

Live products

In progress

Not yet shipped
In development
TB
tankbinder

TankBinder

UST compliance recordkeeping for fuel-tank operators.

In development
DS
operations platform

Dive-shop operations

An operations platform for dive shops.

How I work

The system I built to work this way

I built a system to keep myself consistent as a solo builder. It is not the product, it is how I work.

12 projects 30 specialist agents 25 automated guards 3 independent review gates 6 layers
1Governance

A written rulebook every session inherits: how to work, what not to touch, when to stop.

Shared disciplines Coined shared vocabulary Decision log with the reasoning Per-project charters
2Enforcement

Automated guards that check each action before it runs, so the rules hold under pressure.

Pre-action permission checks Sensitive-data containment Tamper-evident control layer Recoverable-only deletion
3Specialist agents

A fleet of focused agents, each with one job and clear limits, plus independent reviewers that check the work before I see it.

Lane-scoped specialists Independent review gates A quality critic A reviewer that predicts my verdict before I see the work
4Memory

Everything learned is written down and kept, so the system improves instead of forgetting.

Per-agent memory Rollups (daily to weekly to monthly) Search across all projects' history Preserve-only, never deleted
5Routing

Projects hand work to each other through structured messages, never by reaching into each other's files.

Every project has an inbox Work-orders, not direct edits Cross-project requests Symmetric replies
6Lifecycle

Every session starts and ends the same way: orient, work inside the rails, log everything, then I review and approve.

Startup pre-flight Work inside the rails Closeout logging and self-review I review and approve
Self-improvement loop
Failure caught Written down Mechanism fixed New automatic guard Applies everywhere
Cross-project work
Needs out-of-lane work Work-order to another project's inbox Swept at startup Done in-lane Reply to sender
Review before I see it
Build QA Security Release I review and approve
Layer Sub-node Review gate Flow / connector
What I do

Skills and stack

  • Product analytics (Pendo)
  • Building, deploying, and hosting web apps
  • AI developer tools (Claude Code)
  • Customer support & onboarding
  • Clear written documentation

Resume

One-page resume (PDF) Download resume (PDF)

Get in touch

One inbox reaches me directly.