Why the hell in our profession asking: "Why ?" is such a taboo?

Shouldn't it be exactly opposite?

Because the people who set the timelines never learned to ask "why". I always ask why at work, and people keep telling me that it's just a waste of time, so I feel your struggle. It feels like the delivery time importance to quality importance ratio has reached ridiculous levels in this profession. People has just stopped caring almost.

I have been criticized many times because I like to think on the why of every single freaking line of code I write. But I has giving me knowledge I wouldn't have gotten other way.

Why is the most important question unless things are really burning. Then you go for how and then why.

Anyone who does not care about why is a red flag in my book.

While I agree with your comments guys (though personally I have the "luck" to be one and only dev at small company so I'm the one deciding "why"); by my rant I meant inside the community.
The whole don't reinvent the wheel stigma and such.
I just think that there is too much dogmas that we are to take for granted in that way....

@Arlekin, you can ask why without reinventing the wheel. You don't need to create a library that does exactly the same than a well respected one does to answer a why; you could just study it.

Question everything except your ability to question.

When people give me push back on asking why I tell them it is simply my nature to question everything and will continue to happen.

To know as far as knowing can go you have to ask why and see how everything fits together in a larger picture. The usual dislike others have of this question is they fear you're not respecting their authority or are going beyond their control. Sometimes you have to ask and find out why something is to get stuff done in a way that matches reality rather than their delusions of "should." People do not appreciate or understand what actually goes into creating something that works.