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

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
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
Give power saving a settings category of its own: follow battery saver or not, and an economy mode that keeps the heavy effects off
lumenpearson/lessons#445 · opened on Oct 11, 2026 · v1.0.0 — A build somebody else can install
1
In the build console, offer the torrent-like hosting mode only as experimental and not recommended
lumenpearson/lessons#443 · opened on Oct 11, 2026 · Backlog — not scheduled
Let a class admit only the devices its admins approve, bound to a hardware key, with scoped and expiring access
lumenpearson/lessons#442 · opened on Oct 11, 2026 · v1.0.0 — A build somebody else can install
Design: let peers serve a class without being trusted — signed, encrypted, content-addressed snapshots from one primary
lumenpearson/lessons#441 · opened on Oct 11, 2026 · Backlog — not scheduled
5
Research: a beta mode in which devices that join a server lend their capacity as hosting, like a torrent swarm
lumenpearson/lessons#440 · opened on Oct 11, 2026 · Backlog — not scheduled
3
Let anyone run the server on a machine of their own, at home or on a laptop, from one recipe
lumenpearson/lessons#439 · opened on Oct 11, 2026 · Backlog — not scheduled
1
Epic: let any deployment meet 152-ФЗ without changing the code
lumenpearson/lessons#438 · opened on Oct 11, 2026 · v1.0.0 — A build somebody else can install
1

Navigation Menu

Repository navigation

Issues

Issues

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

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

Give power saving a settings category of its own: follow battery saver or not, and an economy mode that keeps the heavy effects off

In the build console, offer the torrent-like hosting mode only as experimental and not recommended

Let a class admit only the devices its admins approve, bound to a hardware key, with scoped and expiring access

Design: let peers serve a class without being trusted — signed, encrypted, content-addressed snapshots from one primary

Research: a beta mode in which devices that join a server lend their capacity as hosting, like a torrent swarm

Let anyone run the server on a machine of their own, at home or on a laptop, from one recipe

Epic: let any deployment meet 152-ФЗ without changing the code