Water retention is something but food that isn't as good or yeild that results in not as good food is a even worse problem too though, the specifics about gypsum should be more researched. I suggested transition metals because it's different and it may be safer but even the alternatives associated with fisher are just as scary for food growth too.
Some of the elements that fisher might use like gypsum, not sure if any of it is safe either though. Soil needs more research, is what most people think but growing things is getting harder not sure if the opensoil project can cover enough of the problems yet.
A more safer alternative might be using transition metals and post transition metals in plant soil. Though using transition minerals usually results in having to be treated with something that can cover coding soil too.
Large repos make sense or don't make sense based on companies that work with large data or not based on predicate calculus and derivatives usually dealing with repos as well as stories and have more problems with ssds too.
There is lots of problems associated with ssds as well as large monorepos.
There are more complicated than people realize but if you did google code jam it teaches them somewhat but needs to be explained too.
There problem is stories sort of intersect with programming too. Clockwork with ssds needs to be reworked for google code jams.
The problem is elixir sort of works with stories and programming. Predicate calculus and proof theories sort of are the only way programming will really make sense in a world full of ssds.
Leveldb could be a more interesting problem for google code jams if it has some newer features too.
Conflict resolution is tower of hanoi and that has problems with consensus algorithms and concat too.SSDs need to do derivatives for pieceing and parting software too and that is more interesting too.
The problem record and replay is expansions of languages and apis too. That is a good thing for some things but it needs to be reworded sometimes too and implementations of things aren't always newer versions of things either.
The problem is clone is more of a start phase after vfork but before fork regardless for github. So it's kind of a bit strange that we call vfork first but that is about templates too.
As for templates they need to be in different languages and in different formats for video games consoles, and so many other formats they port systems and games that sort of work digitally to certain things but not playable to certain things too.
The other problem is that clone is part of syscall interfaces and part of apis and part of a lot of other things too.