Misuse of update/update! in Ruby on Rails

Using `update` (without bang) in Rails without handling its return value leads to silent failures that are hard to debug. When a validation fails, `update` returns false but execution continues normally, potentially causing downstream issues. The fix is to either use `update!` to raise an exception on failure, or explicitly handle the false return value. The RuboCop Rails extension's `SaveBang` cop can enforce this pattern automatically across a codebase.