An audience member asks whether Wójtowicz's 'frequencies' refactor — pulling a fishy piece of code behind a named method/message — is the same as OOP's advice of thinking in terms of messages and grouping methods into cohesive classes. Wójtowicz agrees in spirit: the refactor can be implemented by adding a frequencies method to Array (like ActiveSupport) or by returning a new FrequencyMap class whose only operations are min_value/max_value. The key move is reducing API surface area: making the class 'weaker' (fewer features) increases cohesion, giving you a frequency map rather than a full hash map.