Brian
Colinger

Senior Software Engineer

Building software since 2000.

I've been writing software since 2000 — self-taught, starting in rural Arkansas, eventually working in Silicon Valley, and finding my way back home. I've worked across the stack, but my strengths live in backend architecture, API design, database engineering, and security. I care about systems that are correct, maintainable, and built to last.

These days I'm a Senior Software Engineer at Rebuy, building e-commerce personalization infrastructure in the Shopify ecosystem.

I've worked with AI coding agents every day since mid-2024, and the job has changed. Agents write the code now, and they review it too. My work is deciding what gets built and how, and I'm accountable for what ships. That judgment comes from years of building and debugging systems by hand.

Apr 2023 – Present

Remote

Rebuy, Inc.

Senior Software Engineer

  • E-commerce personalization platform serving thousands of Shopify merchants, across more than a dozen repos
  • Modernizing a legacy CodeIgniter 2 monolith into a CodeIgniter 4 and Next.js platform while keeping production stable
  • Steward of the shared core library and owner of database schema migrations across the platform
  • Backends for billing, ads and monetization, search analytics, automation flows, authentication and team logins
  • Financial reporting for the ads platform, in Go: revenue ledger, API fetchers, BigQuery reconciliation
  • Integrations: Shopify (REST, GraphQL, OAuth, webhooks), Stripe, PayPal, Klaviyo, HubSpot, Cloudflare, GCP Cloud Tasks
  • Several rounds of penetration-test remediation: stored XSS, broken access control, session fixation, CSRF, rate limiting
  • Production incident work: cache stampedes, task retry amplification, webhook delivery failures
  • Stack: PHP (CodeIgniter 4), Go, TypeScript, Python, MySQL, PostgreSQL, Redis, GCP, Cloudflare

Dec 2022 – Jan 2023

Rogers, AR

Shine Solar, LLC

Senior Software Engineer

  • Brought in to modernize legacy CRM from PHP/MySQL to TypeScript, Node.js, and PostgreSQL
  • Introduced team to PostgreSQL, Prisma, Docker, and modern tooling

May 2009 – Jul 2022

Remote

Automattic, Inc.

Code Wrangler

  • 13 years at the company behind WordPress.com
  • Original VaultPress team — built the first security scanner, malware fixers, and site restore system
  • Led development of the WordPress Importer at scale
  • One of a handful of engineers on the Akismet spam detection backend
  • Rebuilt backup and restore infrastructure in Node.js + TypeScript
  • Designed and built RESTful APIs and internal dashboards serving millions of sites

Sep 2006 – May 2009

Sunnyvale, CA

AnchorFree, Inc.

Senior Web Developer

  • Led architecture of a distributed log processing system for advertising analytics
  • Built backend systems for HotspotShield VPN
  • MySQL administration and web property maintenance

2004 – 2006

CA / AR

Earlier Roles

Web Developer

  • Cognizant Technology Solutions (Santa Clara, CA) — On-site developer on a large osCommerce installation
  • Alltel / Western Wireless (Little Rock, AR) — Internal dashboards and metrics tools, LAMP stack

Persistor

GitHub ↗

Multi-tenant remote MCP memory server. OIDC sign-in maps to PostgreSQL row-level security, so tenancy is enforced by the database and not the application. Append-only audit log, retrieval eval harness, self-provisioning test suite. No longer running; the code stays up as a reference.

GoPostgreSQLMCPOAuth 2.1Row-Level Security

Frame Extractors

GitHub ↗

Two CLIs that pull frames out of trail camera video. The Go one runs a worker pool over ffmpeg with hardware acceleration and checkpoint/resume. The Python one keeps only the frames with motion, using background subtraction and blob analysis.

GoPythonffmpegOpenCV

Trail Cam Sorter

GitHub ↗

Sorts raw trail camera video dumps into per-camera, per-date folders by reading the on-screen overlay with OCR. The files carry no usable metadata, so the overlay is the only source of truth.

PythonOCRGPU

Coding Standards

GitHub ↗

The per-language standards I hold my projects and my coding agents to: Go, Python, and TypeScript, with lint configs and Makefile includes so the rules are enforced by tooling and not by memory.

GoPythonTypeScriptLinting

Languages

  • Go
  • PHP
  • Python
  • TypeScript
  • JavaScript
  • SQL

Data

  • PostgreSQL
  • MySQL
  • Redis
  • BigQuery
  • Schema Design
  • Migrations

Backend

  • API Design
  • OAuth2 / OIDC
  • Row-Level Security
  • Webhooks
  • Rate Limiting
  • Session Management

Cloud

  • GCP
  • Cloudflare KV / Workers
  • AWS
  • DigitalOcean

Tools

  • Linux
  • Git / GitHub
  • Docker
  • CI/CD
  • Claude Code
  • MCP

Most of my day goes to directing coding agents instead of typing code. The engineering didn't go away. It moved to the work that happens before and after the code is written.

Where My Time Goes

  • Architecture and data model, decided before any code exists
  • Standards the agents work inside: strict types, linters, tests
  • Splitting work into pieces an agent can finish and verify
  • Checking results against the design, and sending work back when it's wrong

Tools

  • Claude Code — daily driver
  • Claude, ChatGPT, and Grok — personal projects

Have a question, opportunity, or just want to connect? Send me a message and I'll get back to you.