"Writing lots of boilerplate and then figuring out how to reduce it seems wasteful." "You can do the same with much less mucking around with boilerplate by crea

"Writing lots of boilerplate and then figuring out how to reduce it seems wasteful." "You can do the same with much less mucking around with boilerplate by creating data classes first and business logic classes later." That's exactly what the author is trying to argue against. The authors point is that because business logic changes, and that because you can't always be omniscient, it's hard to write the correct abstractions the first time. So although it sounds wasteful to write boiler plate and then abstract, it's less wasteful than abstracting, then coding, and then later having to change it all because you got it wrong.