Team lead: guys, we need to brainstorm on feature X. We can have this service do blah blah..., have a cache at blah blah...

Me: I think it's too complicated. We can simplify the design by doing blah blah... and measure the performance as we go, let's not do premature optimization.

Team lead: no, we definitely need this. We'll pitch this to the CTO later

*Later when we meet the CTO*
Team lead: Hi Mr CTO, about feature X, we're gonna do this blah blah... what do you think?

CTO: *basically repeats what I said*

Team lead: Thank you for the insights, really helpful. We will do as you suggest.

WHAT THE FUCK?

@molaram massive big cocks

Your team lead is a one way valve guy, only takes input from above and dispenses down, not the other way around.

Just like a toilet.

@molaram exactly! I definitely could see how hard he tried to suck managers' cocks.
Our road map indicates big feature Y to be done by end of Q4 2020. One of the top managers: "what if we give your team an extra dev? Will you finish it in Q1?". He agreed with that. As a result, we rushed everything. Luckily no critical bugs happened, but the architecture is a complete mess with tons of technical debts.
During our brainstorm/planning, this often happens:
Him: let's do blah blah...
Me: that won't work because of blah blah... (I give him several bullet points with concrete argument and sources). Also I did the same thing before and got the bitter result. Instead, i think we can do blah blah... These solutions are not perfect but we won't suffer as much.
Him: no, we need to do as I said because it's faster
*Some times later*
Him: wow, that solution was bad, but at least we learned something right? Haha
NO YOU LEARNED SOMETHING. I DID NOT, BUT I HAVE TO CLEAN UP YOUR MESS.