Indeed, the thing that concerns me with YAGNI is the assumptions lurking down below that are never surfaced when someone mentions it to cut a discussion short.

So I joked about YAGNI with some guys in my team and told them YAGNI is like a rock-paper-scissors game; whoever says it first wins!

Daniel

Don't feel bad about yourself: you stood up and took a stand for what you thought was a thing to explain to others. That some of those others didn't agree, so be it. Though it seems as if the 'community' at large tends to get more hostile over the years: whenever someone speaks up, there will always be flames posted, no matter what the subject is. I find that disturbing, it makes it necessary to have a thick skin to stand up and explain something to others, which is IMHO insane.

The point I was trying to make is that YAGNI is one of those things that will always attract criticism whether it's fair or not.

I'm so glad to see this follow up post. I specially like your last sentence, since I believe that to be true, and put in context your first post.

What we try to do in our company when we come up with similar situations is to do the "simples" or "faster" thing at the time, even knowing that is not the best, but we record the technical debt we took, as a case (or user story) for next iterations.

This allow us to move fast and at the same time to have a clear view of what is going to "probably" slow us down later on. Also comunicates this to the client since get's recorded in the backlog.

You've been kicked (a good thing) - Trackback from DotNetKicks.com

Off topic a bit...but your explanation of ["simple" to you isn't the same as "simple" to me.]

This always makes me think back on how to explain Ubiquitous Language as relates to DDD. This is a great example how easily miscommunication can happen.

In this case, even though different parties are using the same words, and in the same context even, the words still have different meanings to different people.

So what's my point? Well, if I have one, I suppose I'm making a case for the importance of Ubiquitous Language. Sorry to hijack your post :P

-Shane

The simplest thing that could possibly work needs to account for "A heap mound of unnecessary complexity surrounding an otherwise simple task " :(

The table *should've* worked and been the easiest, but, due to external factors, wasn't :(

jQuery is useless if you don't have script enabled.  Even a table-based layout is better than a script-based one if you don't have a scriptless fallback.

jkleach@ucdavis.edu