So I proposed a solution to a problem I found. It was deemed a non-problem then by “people”. Some time passed and without my knowing, one of these “people” made an ugly dysfunctional patch to address the said problem. (Implying they’ve come to realise the problem is real.)
Their solution did not fix the problem and introduced more problems.
So now the “people” have approached me and they need me to fix their half-arsed solution and the new problems it introduced.

Now you can be the hero and make a full-arsed solution! :)

This is for me also quite common. I'm often the one that says 'No!' (mostly, because too much work for the time we get, or too complex solution, not worth it). But in the end, if stuff goes wrong, I end up fixing it for the people that said 'yes'. And you know that managers are looking for the first dev that says "Yep, that's possible".

That's often my only issue with beginning devs. Can you do it? "Yes, one hour!". Pff, that's how much I estimate to prepare, create and consume my coffee and cigarette.