Kototama

They did: "Elise [...] worked in the past on Nintendo Switch hacking"

This was written on the original posted page (before the link was changed) when you commented.

If it's for a hobby project it can be fun to work with Common Lisp and see all the good things such an old language still has to offer and where it's still superior to more modern languages. You also don't need to deal with the JVM and will have nice stacktraces (Clojure stacktraces are a mix of Java land and Clojure land). However the ecosystem is very thin so you might have to implement more stuff yourself or being blocked on something (no asynchronous programming for example if you need a very high performance web application). It's not rare to search for a library and find that the last edit was 7 years ago. Maybe it works, maybe it does not, but it surely is not maintained.

The interactivity in Common Lisp is a bit better (navigate the stacktrace, debugger, object inspector etc) but the Clojure REPL is also very good and allow to change the code of your application live without recompiling the whole project. Clojure is a functional programming language, whereas CL is multi-paradigms so it's easier to deal with state in Clojure. The ecosystem of Clojure is much richer and you can always fallback on the endless Java ecosystem if something is missing.

You could have a big external USB drive and try a deduplicating backup software such as borg backup or restic.

You could activate the sshd service and log in to the NAS.

You can use Synology Hyper Backup (or any cloud backup program) and an AWS S3 compatible provider, such as Backblaze.

Books as a unit of time. Interesting :D.

> Typed languages are essential on teams with mixed experience levels

I like this one because it puts this endless dilemma in a human context. Most discussions are technical (static typing ease refactoring and safety, dynamic typing is easier to learn and better for interactive programming etc.) and ignore the users, the programmers.

Because software is built on shifting sands?

You need to cut in the direction of your body in some cases (for example when carving wood).

Two things to prevent injuries: a) never put any force if the material resists b) do it slowly.

It's even more confusing for non native speakers.

You need to preheat the pan and not cook at a temperature where the oil polymerizes or the ingredients can burn. When you put something sticky in it, you need to wait a bit for the crust to form before moving it.

Exactly. Even the Lodge manufacturer, for example, indicates on their website that you can use a small amount of soap.

This is not correlated. Android has sandboxing and you can run your own applications.