we had a "memory leak" because some junior dev didn't know what a closure is, and now we're "solving" it with a "cache busting" proxy server. yeah, that's not a bandaid