We use Google Analytics to see which pages help people. No ads, no profiles. Privacy Policy
36 posts
Compose ships lint rules for the modifier convention, remember misuse, unstable collections and more. Adding your own is how a design-system convention becomes a build failure instead of a code-review comment.
Layout Inspector renders the composition as an inspectable tree with per-composable recomposition and skip counts. Knowing what it can and cannot tell you is the difference between a diagnosis and a guess.
@Preview renders a composable without running the app. Its real value is the pressure it applies: a component that can't be previewed is a component that can't be tested, and both point at the same design problem.
Most of a toolchain is habit rather than measured benefit.
Parallel agents editing one checkout interleave their changes. Isolation costs disk, not correctness.
The annotation lives in an Android artifact, so commonMain cannot use it — and that shapes how you write composables.
A command's promises decay silently through ordinary edits. Per-command assertions plus a fixture that removes one guarantee is what makes the decay loud.
An always-loaded rulebook competes with itself for attention. Matching the tool target and injecting only what fires turns 588 rules into the twelve that apply.
A batch ceiling refuses work without telling you how much exists. Enumerating first turns an unknown amount of work into a finite list you can decide about.
A generated artifact carries no record of how it was made once the process ends. A provenance sidecar makes which-path-produced-this answerable by grep.
A hand-maintained status field said draft for a hundred posts while sixty-eight were live. State that is stored is a memory; state that is derived is a measurement.
A mandatory generation step had produced its fallback on 303 of 304 artifacts, for weeks, because the flag that selected the real path crashed on any real file.
