Thanks for mentioning the safe harbor rule. We are actually aware of that.
The issue here is that the company is asking the payment directly to the company's bank account, or the RSUs will be forfeited forever. This makes the situation much worse IMHO.
Right, the safe harbor rule isn't relevant here. The company is required to do withholding at the time the shares are delivered to you. They've chosen the most burdensome method for you as the only option. I'm not sure there's a way to legally force them to allow a sell-to-cover option, but I really hope so for y'all's sake. This feels really shady.
The shares are not in our brokerage account yet. According to the company, they need to confirm the tax payment to the company before the shares are transferred to the personal brokerage account.
You don’t own shares. You own a right to future shares. Borrow against that. (If you want to roll your own loan, sell a deliverable forward. Again, not legal advice!)
1. There are many services that is already "implemented" in NixOS, with sane default configurations and easy to customize (because the contributors have designed good abstractions, and also because of the flexibility of Nix language). One good example is `nginx`. Btw `paperless-ngx` and `jellyfin` are also already implemented. In this case you do not need to use docker at all.
2. Because of the good abstraction in the service implementation, I usually do not need to go very deep to understand the common configurable options for each of the services.
3. All those services become systemd services once up. As long as you are familiar with how to manage systemd services at runtime, you know how to work with them.
4. Even for those ones that do not exist in NixOS, as the authoer suggested you can still start them as docker-based systemd services, with very simple and intuitive nix configurations.
5. NixOS configuration are mostly deterministic and modular. I can use git to manage all the configurations for different servers. There can be occasions that I will need to migrate the services to a differen machine (e.g. upgrade, replicate, ...). With the NixOS configuration of those services, I can simply re-use the configuration code and have a very high confidence that they will work as expected on a new machine.
6. The above also makes it very easy to revert my deployment to any previous successful version. Without having to worry about breaking anything, it also gives me the confidence to quickly try out different ideas.
The contributors to nixpkgs for the most part, the whole thing is on github and it's one of (if not the) largest Linux package repo of any distro. You can override defaults easily. Security updates are handled by updating your nix channel and rebuilding the system, or updating your flake and a rebuild (if the maintainer has released a more recent version, if they haven't you can make an overlay and bump the version, add your own patches to the build or 'derivation'. Rollbacks are baked in until you remove them from the 'nix store'. You can configure all the things!
1. There are many services that is already "implemented" in NixOS, with sane default configurations and easy to customize (because the contributors have designed good abstractions, and also because of the flexibility of Nix language). One good example is `nginx`. Btw `paperless-ngx` and `jellyfin
2. Because of the good abstraction in the service implementation, I usually do not need to go very deep to understand the common configurable options for each of the services.
I understand `pandas` is widely used in finance and quantitative trading, but it does not seem to be the best fit especially when you want your research code to be quickly ported to production.
We found `numpy` and `jax` to be a good trade-off between "too high level to optimize" and "too low level to understand". Therefore in our hedge fund we just build data structures and helper functions on top of them. The downside of the above combination is on sparse data, for which we call wrapped c++/rust code in python.
In this context, "zero-shot" capability usually means "how well it performs without fine-tuning or prompting with in-context examples" after the model is trained and parameters frozen.
The issue here is that the company is asking the payment directly to the company's bank account, or the RSUs will be forfeited forever. This makes the situation much worse IMHO.