tionate
Joined 4 years ago
Joined 4 years ago
It feels like gardening where slowly your art takes shape, and every single line of code does has a visible impact (no magic) that you can immediately see via the repl
That said, clojure done with AI feels like any other language done by AI. They are interchangeable and thus the language has become irrelevant.
Similarly with AI it is fairly simple to have eg a pre-merge check that validates the commit msg is somewhat useful. This could be implemented for example with GitHub org level checks that must run in a PR.
That said I have no idea how competitive this program is.
In other countries (eg australia), the ticket machines could only take a single coin at a time and would reject if you did it too fast.
I believe this is one (of several) reasons why cash has continued to be dominant in Japan.
Probably the most popular is “kamadosan”. It makes beautiful rice and you have control over it so eg it is easy to create a crust on the bottom if you like.
Unfortunately I have an induction stove now so a bit hard to use, but I occasionally cook rice on a small charcoal stove when enjoying the slow life.
Review: https://thejapanesefoodlab.com/kamado-san/ Recipes: https://toirokitchen.com/blogs/recipes
- it is not really any more lines - doesn’t break if dev upgrades to a different version of the resource (has happened before) - allows you to experiment with dev with other setups (eg additional ingresses, different paths etc) instead of changing a base config which will impact other envs
TLDR patch things that are more or less the same in each env; create complete resources for things that change more.
There is a bit of duplication but it is a lot more simple (see ‘simple made easy’ - rich hockey) than tracing through patches/templates.
You can fairly quickly get to a point where your investments go up (or down, but more often up) more in a day than your monthly income.