A DI module that compiles on every target and only works on one
Registration is common. The bindings are not. DI defers the error to first use, which is usually on a user's device.
architecture
98 posts
A platform bridge is an interface with a lifetime problem
Permissions, biometrics and share sheets all need something shared code does not have: a host that outlives the call.
kotlinx.serialization is compile-time, which is why your polymorphism fails at runtime
No reflection on Native, so the serializer is generated. Sealed hierarchies work; open polymorphism needs a module you register by hand.
Following one rule turned a passing gate into 16 failures. Both rules were right.
Two policies, each locally correct, sharing one assumption nobody owned.
Senior engineers decide without complete information. Here is the method
The skill is not better judgement. It is knowing which kind of door you are standing at.
Most code review approves code. Here is review that improves it
Line-level comments are the least valuable thing in a review. Three questions outrank all of them.
A ceiling in a conditional is one someone deletes
A budget expressed as a value can be read, derived from and audited. Buried in a conditional it can only be obeyed or removed, and it gets removed.
Loading every rule up front is how none of them apply
An always-loaded rulebook competes with itself for attention. Matching the tool target and injecting only what fires turns 634 rules into the twelve that apply.
Editing the generated thing is how the spec stops meaning anything
A change implemented directly in source skips the spec, so every report downstream is computed without it. The feature works and nothing can see it.
Every generated file should say what made it
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 generator given the wrong context does not stop
Scoping a context pack by project type saved 12.6% per subagent, not the 40% I guessed. The real risk is a thin pack: a missing surface makes a generator invent.
Two places that both think they are the truth
A durable source of truth and an in-memory one give the same answers until a process dies. Deciding which is authoritative is a design act, not a default.