Junilu Lacar wrote: If it's always today's and yesterday's data that are being merged, it might be better to leave that information out of the name and put in the documentation.
Junilu Lacar wrote:
I don't know if the word "data" is really needed. What does the data represent? That would probably be the better word/phrase to use in the name instead of just the generic "data" idea.
Junilu Lacar wrote: For example, add_current_day_total_with_past_day_total might just be calculate_weekly_running_total.
Junilu Lacar wrote: Think at a higher level of abstraction and less at the implementation level when trying to find good names.
Tim Holloway wrote:but avoid mixed cases in c_like_names or underscores in javaLikeNames.
Monica Shiralkar wrote:
But should that not be in the context that what kind of data it is .E.g whether it is weather data or stocks data ?
Monica Shiralkar wrote:input_data , processed_data are relatively more meaningful than data.
I found currentDay_inputData (mixed of snake case and camel case) is easier to understand than current_day_input_data but the latter and not the former follows the python naming standards.
Matthew Bendford wrote: your write function: write(output)
There's no need to add "data" to anything in any case.