Thank you, keep it as it is, it's just great!
I'm working together with my son's teacher, who is also working at a local school. It's for kids that might not have the privilege of getting private lessons. I'm a backend developer, but I fell in love with Elm and built the site entirely with it. I host it on GCP.
I'd like to build a template system to support multiple languages, but I'm not sure the so-called calculation strategies kids in the Netherlands learn are the same for kids in other countries.
If you have kids in primary school: please give it a try and let me know what you think?
2. Children of Time - a science fiction book that I enjoyed, I notice that fiction, in general, helps me deal with stressful work, as I disconnect easier and put myself in an imaginary world while reading;
3. Meditations by Marcus Aurelius - this isn't a book you read cover to cover, I catch myself thinking long even after reading a single sentence;
1) and 3) I've come across on HN, but 2) was the unexpected random hit.
It is always a steep curve to dive into other developers code.
my very first consulting project (yes, i had absolutely no experience), around that time, was implementing blaze advisor (now owned by fico: http://www.fico.com/en/products/fico-blaze-advisor-decision-...) to migrate a mainframe-based automated life underwriting system to a j2ee client/server system.
performance was a major concern, so i read Forgy's 1982 paper about RETE (that i didn't quite understand frankly), but the key takeaway (for me at least) was that all the hard work happened during compilation so running performance shouldn't be an issue. from what i dimly remember, the algorithm iterates through the rules set building something akin to a decision tree until the tree reaches a stable state. if it never reaches stability, it will throw a compile error. once the tree is built, matching is very fast.
the holy grail was that "business analysts" (remember when that title was in vogue? =) could write the rules, saving you months of precious time and thousands of dollars by not paying programmers (it did not turn out that way of course).