«You can say the same thing about the food in any restaurant.»
Except you also have more accumulated debug time/expertise in a typical restaurant. Soylent tries to do a lot of things from first principles that otherwise people have spent many years building: food supply chains, logistics, recipes, kitchen procedures, etc.
Bringing it back to a code analogy, too, most restaurant food is "naturally" a more loosely coupled component model and it is easier to isolate components when debugging (no mayo, hold the lettuce), whereas Soylent is very tightly coupled and it shouldn't be surprising that it may suffer some of the same maintainability concerns in the long run.
Except you also have more accumulated debug time/expertise in a typical restaurant. Soylent tries to do a lot of things from first principles that otherwise people have spent many years building: food supply chains, logistics, recipes, kitchen procedures, etc.
Bringing it back to a code analogy, too, most restaurant food is "naturally" a more loosely coupled component model and it is easier to isolate components when debugging (no mayo, hold the lettuce), whereas Soylent is very tightly coupled and it shouldn't be surprising that it may suffer some of the same maintainability concerns in the long run.