←back to thread

1070 points dondraper36 | 1 comments | | HN request time: 0.323s | source
Show context
Scubabear68 ◴[] No.45070901[source]
I get it.

YAGANI.

A term coined by consultants who don’t understand an industry who basically say “do the least possible thing that will work” because they don’t understand the domain and don’t understand what requirements are often non-negotiable table stakes of complexity you need to compete.

It reminded me of a Martin Fowler post where he was showing implementation of discounts in some system and advocating to just hard code the first discount in the method (literally getDiscount() {return 0.5}).

Even the most shallow analysis would show this was incredibly stupid and short sighted.

But this was the state of the art, or so we were told.

See also Ward Cunningham trying and failing to solve Sudoku using TDD.

The reality is most business domains are actually complex, and the one who best tackles that complexity up front can take home all the marbles.

replies(2): >>45070970 #>>45075240 #
1. gavmor ◴[] No.45070970[source]
Undoubtedly, Fowler suggested this as an incomplete step in the development process, essentially to get the code to compile.

Incredible that we can tar both complexity and simplicity with the brush of "consultant BS."