[pritambaral]

> Under engineered code tends to be simple, straightforward work with a low blast radius

Under-engineered code can easily become over-engineered code, while retaining the appearance of being the former, as engineers keep working on it over time. It only becomes easier over time, as bugs are uncovered by users and then "fixed", as features are requested by users and then bolted on, and so on.

> If I get a task to "make the button blue" I'd rather do it in a repo where I need to grep around a little than in ...

In the kinds of codebases I'm talking about, you will successfully end up making the button blue, but then, either:

1. sth else breaks and you wouldn't know about it until later; and/or

2. a bunch of seemingly unrelated tests break and you will need to debug which button provider is auto-injected into which tests' setup routines.