Doing it more can provide better result only when it is allowed to trash the previous iterations to use the latest one.
This is not the case in the industry, we cannot change everything in a product at each iteration. This is why at least a little care and architecture have to be done before doing it and trashing must be made with care.
Fine to setup.
But I don't understand how to reload a project after closing the REPL.
More generally, too many tools to master and understand...
And didn't find a simple tutorial to start with the ecosystem.
Your processes made me think about a email based interface instead of a bash script, this may allows to easily interact with the database bot without knowing bash or python.
Adding a dead boolean field, then all the entities with links removes their pointers when possible by looking at the dead field, at the end the object is freed.
They always uses a white background.
Is it working well with a non white background?
Generally the detection is more complicated with a different background.
I think existing incentives are working fine, except of
course that I wish more people would discover the
advantages of literate programming.
The problem, is, in my opinion is that programmer believes in the beauty of code itself, and literate didn't allow to write beautiful code easily.
It helps to write beautiful documentation.
Maybe a tool allowing literate and inverse literate programming to propagate modifications in code or in documentation on both directions may allow a better adoption?