Repository navigation

Issues

New issue

Epic: one proto contract — REST v2, Connect and native gRPC, decomposition, build console
#273 · lumenpearson opened on Oct 3, 2026
1
Epic: v1.0.0 — a build somebody else can install
#127 · lumenpearson opened on Sep 22, 2026

A write whose class or bell schedule another writer deletes mid-write fails on a foreign key, which nothing catches
lumenpearson/lessons#662 · opened on Oct 18, 2026 · v0.10.0 — One contract: REST v2, Connect and native gRPC, build console
Nothing checks that the files, tests and commands the agents and skills name still exist, so an agent can be sent to a file that moved
lumenpearson/lessons#661 · opened on Oct 18, 2026 · Backlog — not scheduled
The test counts are hand-edited in seven documents on every batch, and the gates skill once said 770 Android tests when there were 1635
lumenpearson/lessons#660 · opened on Oct 18, 2026 · Backlog — not scheduled
The gate commands live in three hand-kept lists — CLAUDE.md, settings.json's allow list and ci.yml — and bare pytest was in only two of them
lumenpearson/lessons#659 · opened on Oct 18, 2026 · Backlog — not scheduled
A timetable import whose bell schedule another writer deletes mid-write answers a server error
lumenpearson/lessons#657 · opened on Oct 18, 2026 · v0.10.0 — One contract: REST v2, Connect and native gRPC, build console
More writes still answer a server error when another writer deletes their row mid-write
lumenpearson/lessons#654 · opened on Oct 18, 2026 · v0.10.0 — One contract: REST v2, Connect and native gRPC, build console
CLAUDE.md is read by every session at about 27 thousand tokens, and a third of it is the record of how a rule was learnt
lumenpearson/lessons#648 · opened on Oct 17, 2026 · Backlog — not scheduled
Two pull requests that each pass against the old main can break the new one together, and the ruleset does not test the merge
lumenpearson/lessons#646 · opened on Oct 17, 2026 · Backlog — not scheduled
A test that fails once and passes alone is found only if somebody reads the red run, and no rate is kept
lumenpearson/lessons#645 · opened on Oct 17, 2026 · Backlog — not scheduled
ruff selects five rule families, and none of them catches a naive datetime.now() on a server whose time belongs to the class
lumenpearson/lessons#644 · opened on Oct 17, 2026 · Backlog — not scheduled
mypy asks one question of 240 modules, and nothing moves it towards asking more
lumenpearson/lessons#643 · opened on Oct 17, 2026 · Backlog — not scheduled
Which side of the merge a migration goes on is decided by reading its DDL, and nothing checks the decision
lumenpearson/lessons#642 · opened on Oct 17, 2026 · Backlog — not scheduled
A merge to main deploys to production and nothing asks the new deployment whether it works
lumenpearson/lessons#641 · opened on Oct 17, 2026 · v1.0.0 — A build somebody else can install
Nothing asks a v1 read and its v2 twin the same question over the same data, so the two can answer differently
lumenpearson/lessons#640 · opened on Oct 17, 2026 · v0.10.0 — One contract: REST v2, Connect and native gRPC, build console
The app's JSON tests decode payloads copied by hand from the server's schemas, so the two can drift together and both stay green
lumenpearson/lessons#639 · opened on Oct 17, 2026 · v1.0.0 — A build somebody else can install
Nothing compares /api/v1's schema with the previous one, so a change installed apps cannot read passes CI
lumenpearson/lessons#638 · opened on Oct 17, 2026 · v1.0.0 — A build somebody else can install
A feature that misbehaves on installed phones can only be switched off by a new APK
lumenpearson/lessons#637 · opened on Oct 17, 2026 · v1.0.0 — A build somebody else can install
A crash on an installed phone reaches nobody unless its owner turns on the debug mode and sends the report
lumenpearson/lessons#636 · opened on Oct 17, 2026 · v1.0.0 — A build somebody else can install
Nothing stops a detekt baseline from growing: detektBaseline can absorb a new finding and the diff looks like a move
lumenpearson/lessons#635 · opened on Oct 17, 2026 · Backlog — not scheduled
The Kotlin traps CLAUDE.md lists are caught by reading: no rule fails on LocalDateTime.now(), ZoneId.systemDefault() or Russian text in Kotlin
lumenpearson/lessons#632 · opened on Oct 17, 2026 · Backlog — not scheduled
No test presses every control a screen draws, so a crash on a press in an unusual state is found by a user
lumenpearson/lessons#629 · opened on Oct 17, 2026 · Backlog — not scheduled
Screens have no canonical states: previews exist for components only, and every Compose test invents its own UI state
lumenpearson/lessons#628 · opened on Oct 17, 2026 · Backlog — not scheduled
No screen and none of the widget's twelve sizes has a screenshot test, so a visual regression between two device walks is invisible
lumenpearson/lessons#627 · opened on Oct 17, 2026 · Backlog — not scheduled
Epic: take the engineering practice Airbnb has published where it fits — tests at the screen's state, a contract installed phones can read, lessons as rules
lumenpearson/lessons#626 · opened on Oct 17, 2026 · Backlog — not scheduled
The deployment guide and the README describe one deployment as the project's own: its proxy provider, its cron job, its Sentry and Vercel accounts
lumenpearson/lessons#471 · opened on Oct 16, 2026 · v1.0.0 — A build somebody else can install

Navigation Menu

Repository navigation

Issues

Issues

A write whose class or bell schedule another writer deletes mid-write fails on a foreign key, which nothing catches

Nothing checks that the files, tests and commands the agents and skills name still exist, so an agent can be sent to a file that moved

The test counts are hand-edited in seven documents on every batch, and the `gates` skill once said 770 Android tests when there were 1635

The gate commands live in three hand-kept lists — CLAUDE.md, settings.json's allow list and ci.yml — and bare `pytest` was in only two of them

A timetable import whose bell schedule another writer deletes mid-write answers a server error

More writes still answer a server error when another writer deletes their row mid-write

CLAUDE.md is read by every session at about 27 thousand tokens, and a third of it is the record of how a rule was learnt

Two pull requests that each pass against the old `main` can break the new one together, and the ruleset does not test the merge

A test that fails once and passes alone is found only if somebody reads the red run, and no rate is kept

ruff selects five rule families, and none of them catches a naive `datetime.now()` on a server whose time belongs to the class

mypy asks one question of 240 modules, and nothing moves it towards asking more

Which side of the merge a migration goes on is decided by reading its DDL, and nothing checks the decision

A merge to `main` deploys to production and nothing asks the new deployment whether it works

Nothing asks a v1 read and its v2 twin the same question over the same data, so the two can answer differently

The app's JSON tests decode payloads copied by hand from the server's schemas, so the two can drift together and both stay green

Nothing compares `/api/v1`'s schema with the previous one, so a change installed apps cannot read passes CI

A feature that misbehaves on installed phones can only be switched off by a new APK

A crash on an installed phone reaches nobody unless its owner turns on the debug mode and sends the report

Nothing stops a detekt baseline from growing: `detektBaseline` can absorb a new finding and the diff looks like a move

The Kotlin traps CLAUDE.md lists are caught by reading: no rule fails on `LocalDateTime.now()`, `ZoneId.systemDefault()` or Russian text in Kotlin

No test presses every control a screen draws, so a crash on a press in an unusual state is found by a user

Screens have no canonical states: previews exist for components only, and every Compose test invents its own UI state

No screen and none of the widget's twelve sizes has a screenshot test, so a visual regression between two device walks is invisible

Epic: take the engineering practice Airbnb has published where it fits — tests at the screen's state, a contract installed phones can read, lessons as rules

The deployment guide and the README describe one deployment as the project's own: its proxy provider, its cron job, its Sentry and Vercel accounts