Is Design Dead?

Through my journey on the realms of coding, I have always felt somehow fond of this philosophies and techniques alike to XP, I see all of those processes of heavy documentation that the waterfall methodology had and I surely feel that it is just a glorification of unnecessary software bureaucracy. However I have to agree with the point of view of the author on this one. As much as I love living in a time where you can attend to your daily scrum meeting wearing your worn out jeans as it is in most big IT companies that follow the current fashion, there will always be a place or two were it is justified that a programmer should be wearing a tie and a sweaty neck. Just as ties are not dead, design is still living for projects that demand flexibility.
As it is stated, XP relies heavily on delivering value as soon as possible. This implies that components that are not essential to the functionality at the time to deliver should be ignored. The way to deal with time for XP enthusiasts is sticking with the YAGNI but valuing the skills that are essential for software design. Seemingly, extreme programmers need to have a clear vision of what the design of the system is at the time of building a single module. This enhances the damage mitigation at the time of implementing new feature in a production environment. 
Perhaps I might be wrong but as much as Kent Beck is quoted and also considering that XP requires developers to catch errors as early as possible Test Driven Development might be a start point for XP however this philosophies seem to contradict the very core of YAGNI. I believe that a clever team should always find a balance between delivering and designing.