>A good example of this trade-off in Java is Lombok. A very handy library that legitimately avoids a ton of boilerplate, but it also absolutely tanks your build time.

I don't think this is actually true right now and for a while.

>In a real system, a large one, your team is better off just getting good enough with their editor that they can generate the hateful boilerplate

Which you can get by delomboking if you really need to.