You're right, that's a terrible answer. But not because the content is bad, but because you threw a coworker under the bus and because you didn't mention the im

You're right, that's a terrible answer. But not because the content is bad, but because you threw a coworker under the bus and because you didn't mention the impact that any of these changes had. "We had a large module that we were making lots of changes to that used Python decorators to add behavior. This pattern ended up growing to be really difficult to debug as we were changing the code, and when tests would break it would take hours of tracing through the code to figure out the reason. I (rewrote each method to not use decorators | inlined the decorators manually | whatever) to clean up the code. One of the other reasons working with this module was difficult was because the documentation was terrifyingly out of date, so as I was cleaning up the decorators I also updated the documentation." If you can say anything about the quantifiable impact, then do it, but I don't think this example necessarily requires it. The meetings had nothing to do with your problem.