pozorvlak
pozorvlak
+1. Some thoughts: - **Smart test-runners**: I looked into various gems for preloading tests or only running relevant tests soon after the project started, but the number of stale-cache problems...
Cool! I expect we'd want some kind of "export as ICS/RSS/etc" feature, so people could include their gardening diaries in Google Calendar or whatever.
I suspect any attempt to limit this to "fruit" etc will be defeated by the infinite cussedness of biology. Maybe we need a `harvesting_produces_seeds` boolean field on `Crop`?
"Each crop has some seed saving instructions" sounds like the simplest thing that could possibly work - let's start with that.
Also, the crop hierarchy doesn't always line up with genus/species boundaries (deliberately - consider all the different varieties of _Brassica oleracea_!)
> the number of varieties, even morphologically very distinct varieties, > within a species is not a barrier to a concept of hierarchy in a crop model. > > Indeed...
Sounds like a plan, though we'll probably have to think about how events interact with harvests.
They could definitely be related, but I think the causality might go the other way - exceeding our RAM quota means we're hitting swap, which will slow page-loads way down....
I think the blue dot and sudden drop in RAM usage at 8am in the graph above is us getting killed for exceeding our quota too flagrantly. But from https://devcenter.heroku.com/articles/ruby-memory-use#why-memory-errors-matter:...
@apdarr Thanks!