So I already discussed this with kab, but posting here for the edification of the masses...
One of the things I found interesting (in addition to all the stuff above) is the approach to food waste. The first steps in a lot of what we were doing was to cut of sides/tops/bottoms of the fruit and veg, and discarding those off-cuts, partly to get things a regular shape for the sake of appearances and of consistent cooking times, but also because it's a lot quicker to safely cut vegetables that are already a regular shape.
The obvious parallel here to me is with one of the design principles of the Python programming language: staff time is expensive, being less efficient with (food waste|computer memory) is comparatively cheap, therefore it's worth discarding food that's perfectly edible / writing code that's not as fast as it could be, because the labour cost is higher than the value lost through the inefficiency.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
regna
(no subject)
Date: 2019-05-05 12:10 pm (UTC)One of the things I found interesting (in addition to all the stuff above) is the approach to food waste. The first steps in a lot of what we were doing was to cut of sides/tops/bottoms of the fruit and veg, and discarding those off-cuts, partly to get things a regular shape for the sake of appearances and of consistent cooking times, but also because it's a lot quicker to safely cut vegetables that are already a regular shape.
The obvious parallel here to me is with one of the design principles of the Python programming language: staff time is expensive, being less efficient with (food waste|computer memory) is comparatively cheap, therefore it's worth discarding food that's perfectly edible / writing code that's not as fast as it could be, because the labour cost is higher than the value lost through the inefficiency.