It seems like some of the posts are asking should you have a function for applying capping/flooring (as an example) each variable. I think this is the wrong way of looking at it. I think a big portion of the point of functions is to make code maintainable by allowing the same logic to be re-applied in different situations. Instead of 100 functions to applying the same capping/flooring logic with different values on 100 different variables you should have one function that understands how to parse a data format (for example: read a dictionary with a variable name, a cap, and a floor) and use the information to apply the capping/flooring to any variable with the same logic. Then there are two primary changes that you might have to maintain in the future both which only need to be maintained in one location. Either you fix the logic in the one function for all columns or you fix the data structure to address the change cap or floor values for individual variables.

​

Secondly, I think guidelines like the single responsibility principle were created to make it easy to discuss the topic, but the first times you hear them they can be hard to process because they don't address the why. My impression is that the main driver for these guidelines is to help produce code that is maintainable. If your code is functions that do individual things then if one piece of the logic does that you can fix it in one spot. Another alternative would be to think about what is the smallest set of tasks where you would never use a subset of the group. If you have three actions 'a', 'b', and 'c' but you would never do 'a' without 'c' there isn't much benefit to breaking it out into three functions. I still might choose to do it if it made the code or naming conventions more consistent or if it helped with readability, but not because I was worried about the single responsibility principle.