When I saw Google allowing users to remove the visible watermark from AI-generated images, my first reaction was: isn’t this just commenting out the line with console.error?
On the surface it’s clean—the invisible watermark is still there. If anything goes wrong later, you can still trace it back; it’s just that users can’t see it. We developers often do things like this too: swallow the errors, lower the log level, and we all know in our hearts the problem hasn’t actually been fixed.
But the product manager sees that the interface no longer errors and thinks it’s been fixed. In the end, the one who originally commented out that error is still the one who gets blamed. 🤡
On the surface it’s clean—the invisible watermark is still there. If anything goes wrong later, you can still trace it back; it’s just that users can’t see it. We developers often do things like this too: swallow the errors, lower the log level, and we all know in our hearts the problem hasn’t actually been fixed.
But the product manager sees that the interface no longer errors and thinks it’s been fixed. In the end, the one who originally commented out that error is still the one who gets blamed. 🤡