Considering the biases, the one I wrote for the company I created.
When we have the opportunity to be in this context, keeping in mind what bothered us in the codebases with which we were able to work in the past, we can force ourselves not to reproduce the same errors. Like the unmaintained unit and integration tests, the lack of refactoring, other developers that use fancy technologies instead of simpler concepts more for the opportunity to play with technologies than real need..
And also, I guess, because we are more aware that the code is a reflection of the company that we want to have, that the simpler the better is a key point when we need to debug.
Agreed. From what I know, the positive points of certain alcohols such as wine which would protect against heart problems have either been denied, or the same advantages have been found in everyday non-alcoholic products (green tea if I remember well).
In France, where I am, awareness campaigns recommend sticking to a maximum of 2 glasses per day, for men, 1.5 for women. and not every day.
And these values only take into account protection against serious health problems, such as stroke, not the problems of moderate daily alcohol consumption, such as for example the fact that alcohol being a depressant, consumption will have a impact on their general well-being.
To be honest, I'm even more confused on what to think about this paper.
I would be very interested, if somebody can access the full paper, to know what amount of alcohol is "light drinking" for them.
2 glasses a day ? a week ? a month ? with people ? during dinner ?
Not sure I understand right what this article is about.
From my point of view, CSV is an easy way to export data from a system to allow an end user to import it in excel and work on this data.
Apart if it's as easy with parquet to import in excel as with a CSV, I'm not sure this is not fixing a problem that doesn't exist. And making things more complicated.
Outside of the context of end user, I don't see any advantages in this compared to xml or json export.
When we have the opportunity to be in this context, keeping in mind what bothered us in the codebases with which we were able to work in the past, we can force ourselves not to reproduce the same errors. Like the unmaintained unit and integration tests, the lack of refactoring, other developers that use fancy technologies instead of simpler concepts more for the opportunity to play with technologies than real need..
And also, I guess, because we are more aware that the code is a reflection of the company that we want to have, that the simpler the better is a key point when we need to debug.