breakds

We use NixOS and Nix extensively in the company. A few developers actually use NixOS on WSL as daily driver, and it was pretty smooth.

I would second this. Learning nix takes time and practice, but is very rewarding. Reading the nix pills series is definitely the most helpful first step. I would also recommend https://discourse.nixos.org/ where kind fellow Nix users constantly answer questions and give advice.

The home I live in is viewed as a consumption instead of investment to me. I would try to really limit my expense on buying the primary residency home, and if there are $ left, invest them.

As a former professional Lisp programmer, I think the Nix language was pretty good. Not the easiest to pick up but I like writing it very much once getting used to it.

But everything is connected. Beware of the fluctuation/crisis in the other markets which might be triggered by what's happening in the crypto market.

My router is also a pretty old Intel Nuc running NixOS (https://github.com/breakds/nixos-routers/blob/main/machines/...). It has been very smooth and easy to maintain.

I really like the idea of the game. Super fun!

+1. I feel the same as OP after leaving Google. However, after switching to Nix, I had a greater experience working with projects (with mulitple languages), even better than the mono repo at Google.

I have been running NixOS and uxing Nix for almost everything since I switched to it, and my experience has been great so far. It is one versatile solution to a lot of applications:

1. I run NixOs on on laptop and workstation, for work and for personal use. Any change to the configuration can be immediately transfered to other machines. And give me a new machine, I can quickly bring it up with the configuration that I am always using. 2. I run NixOS on my home server and machine learning cluster. Deploy experiment and service on them is as simple as updating the git-managed configurations. Meanwhile, if I want to use more power to run an experiment, NixOps can quickly bring up a set of machines on AWS with the configuration identical to my local experiment. You do not need to worry about setting up CUDA/pytorch and other dependencies every. 3. In my start-up, it definitely took more time to train the developers to learn Nix, but once they get familiar, everyone becomes a good DevOps engineer, which solves development environemnt (that invloves C++/Python), CI/CD and release really well.

If you are aiming at the industry, I would say getting a research-oriented master's degree is much more cost-effective. Besides you can always learn the skills you need in your work.

Yes. The core of the backend is still in Common Lisp (and C++). Many ITA hackers are still contributing to the Common Lisp community :)