For the right set of requirements I can fix bugs in my system with significantly less effort, than rewriting a system which was built with wrong assumptions to begin with.
Again, wrong analogy. I don’t demand perfect analogies though. Treat this as rather charitable gesture.
You can also argue that good devs translate requirements into code perfectly with zero bugs, but it's also a rare skill and I've never seen that.
Because in the real world, nobody's perfect. The good news is you don't need to be perfect to still add lots of value.
Demanding a standard of perfection from others, that I would hazard to guess you do not meet yourself, is rather uncharitable.