YAGNI and KISS appears dead in most shops. What-if fears gum up stacks. "You should pick a stack that has internationalization, microservices, web scale, respon

YAGNI and KISS appears dead in most shops. What-if fears gum up stacks. "You should pick a stack that has internationalization, microservices, web scale, responsiveness (finger and mouse usage), accessibility, etc. etc." In practice most orgs don't actually use or need all that, yet pay the "complexity tax" to have it. Might as well buy meteor insurance while at it. Somebody needs the guts to say "no" to too much junk in the trunk. I take a scoring hit when I say accessibility often goes unused for small/niche biz apps and thus should be skipped or downplayed in some cases, but it's the blunt truth. ADA laws say "reasonable". The cost/benefit math is often not reasonable in many situations, and I'll take the case to the jury myself if necessary. Ignoring YAGNI is economically costly. A lot of it is also caused by dev's trying to get as many buzzwords on their resume as possible. Between Resume Oriented Programming and managers' fear-of-missing-out, we have bloated stacks and bloated software. YAGNI and KISS matter, but ignored by silly human tendencies. I think I'll find a job on Vulcan...