When do the SOLID principles become YAGNI?

As programmers we make trade-offs all the time, between complexity, maintainability, time to build and so forth. Amongst others, two of the smartest guidelines for making choices are in my mind the SOLID principles and YAGNI. If you don't need it; don't build it, and keep it clean.

Now for example, when I watch the [dimecast series on SOLID](http://www.dimecasts.net/Casts/ByTag/SOLID%20Principle), I see it starts out as a fairly simple program, and ends up as a pretty complex one (end yes complexity is also in the eye of the beholder), but it still makes me wonder: when do SOLID principles turn into something you don't need? All solid principles are ways of working that enable use to make changes at a later stage. But what if the problem to solve is a pretty simple one and it's a throwaway application, then what? Or are the SOLID principles something that always apply?

As asked in the comments: 

* [SOLID Principles](http://en.wikipedia.org/wiki/SOLID_%28object-oriented_design%29)
* [YAGNI](http://en.wikipedia.org/wiki/You_ain%27t_gonna_need_it)