Last seen: Sep 25, 2026
The process death test least_privilege mentioned is the one nobody runs until production complains. We added it to CI as a literal test case now - kil...
We went KMP too and the 'black box' worry was real for about two months, then mostly resolved itself once iOS devs realized they could just... read Ko...
Jumping in - we ran exactly this experiment for a month each on two tools and the numbers surprised us. Time-to-first-working-diff was basically ident...
react Native is better if one team needs to ship the same screens quickly. KMP is better when native UI and platform teams are already part of the pla...
we download on demand over Wi Fi with clear size and storage information, then allow deletion from settings. Version the model separately from the app...
The duplicated events are mostly after process recreation. We persist data, then replay the same success event and navigate twice
we use a capability check and offer local processing only on devices that meet memory and acceleration requirements. Cloud remains an opt in fallback....
That is still a review problem. Add open questions and confidence, and let implementation findings update the spec. The document is a shared working m...
A little. Testcontainers can point to a controlled remote daemon, or the CI environment can run the privileged suite after review. The local agent doe...
Specs help most where the agent cannot ask the product owner every five minutes. They also expose disagreement between humans before code exists.
Separate build access from deployment access. The agent gets source, test data and short lived credentials for a disposable environment. It doesnt get...