Skip to case study
All selected work

Product engineering & developer tooling

LineCrush

From the first commit to daily operation.

I started the LineCrush codebase in 2024. Jay and I built it into a sports research platform, then extended the product to native apps and built the engineering system that helps us keep shipping.

Jump to C2 & the agent fleet
LineCrush sports research app shown in its official store screenshot
The released LineCrush app. Official App Store screenshot.
My role
Co-founder & CTO
Result
Live on web, App Store & Google Play
Timeline
2024 to present
Next.jsTypeScriptPythonPostgreSQLSwiftUIKotlin

Build the product, then stay responsible for it.

The first implementation was mine. As the company grew, Jay and I developed the product together, from the web experience to the services behind it. My work spans application code, data, infrastructure, native clients and release engineering.

That ownership continues after a feature lands. Account state, loading behavior, release failures and the first experience for a new user are part of the product too. The work is making those pieces hold together in production.

Native apps started with working user journeys.

I scaffolded the SwiftUI app in June 2026 and built its first research cards, search, filters, stats and insights. Later that month I started the Kotlin and Jetpack Compose client, including its API client, authentication and swipeable research deck. Both use the existing product backend.

App Review exposed a case our demo account had missed. A fresh account with no history hit an error. I traced the review requests, reproduced the failure on an iPad simulator, and fixed the empty state. That experience made the new-account journey part of what a release has to prove.

The Android app reached Google Play in August 2026 and iOS reached the App Store in September. The fleet now carries substantial implementation and release work across both clients. I built the foundations and the delivery system, and the ongoing product is a team effort.

C2 and the engineering fleet

I designed the engineering agent fleet and C2, the tracker we use to carry work from an issue through delivery. Jay and I operate it together. Durable work history means an interrupted run doesn't have to erase what was already learned or built.

C2 brought roughly 19,000 historical issue records into the same system as new work. It connects the request, the run and the delivery evidence, so a completed task has something concrete behind it. The engineering pattern is investigate, implement, verify the actual product, review, ship and check the result.

Completed fleet jobs
14,111
Completed jobs with a recorded commit URL
10,745

Job ledger snapshot, . Completed work includes investigations and documentation. The second figure counts job records that contain a commit URL.

A public result

NFL first-quarter statistics, in the released app.

The iOS 2.9.0 release notes list first-quarter passing, rushing and receiving leaders in Signals. The underlying delivery record connects this feature to completed team and fleet work. It's one concrete example of the system contributing to a product people can use.

Read the App Store release notes (opens in a new tab)
Read the published fleet walkthrough

What I take forward

Starting a product is one kind of work. Keeping its accounts, clients, releases and engineering process coherent is the work I want to keep owning.