Find the proper driver at the NVidia website.
Note: Make sure to select "Linux 64-bit" as your OS
Hit the "Search" button.
variant: fcos | |
version: 1.4.0 | |
passwd: | |
users: | |
- name: testuser | |
groups: ["wheel", "sudo"] | |
#ssh_authorized_keys: | |
# - <your SSH public key> | |
systemd: | |
units: |
Find the proper driver at the NVidia website.
Note: Make sure to select "Linux 64-bit" as your OS
Hit the "Search" button.
I'm writing this gist for my own records but it might help someone else too.
Support for Catalina has improved a lot since the update was first rolled out.
Note: See the NixOS manual for discussion of the --darwin-use-unencrypted-nix-store-volume
option.
This guide provides instructions for an Arch Linux installation featuring full-disk encryption via LVM on LUKS and an encrypted boot partition (GRUB) for UEFI systems.
Following the main installation are further instructions to harden against Evil Maid attacks via UEFI Secure Boot custom key enrollment and self-signed kernel and bootloader.
You will find most of this information pulled from the Arch Wiki and other resources linked thereof.
Note: The system was installed on an NVMe SSD, substitute /dev/nvme0nX
with /dev/sdX
or your device as needed.
/** | |
provide an array of audio files urls and get them merged | |
Its important to note that the process is asynchronous and that one would need to show user some sort of a progress indicator | |
so that the process does not get interupted | |
- parameter audioFileUrls: an array of audio file urls | |
- returns String representing the newly merged file or nil for a failure | |
*/ | |
func mergeAudioFiles(audioFileUrls: [URL]) -> String? { | |
let composition = AVMutableComposition() | |
The art of making waffles is very similar to the challenges in team software development. Things have to be prepared on time, and instructions have to be followed. The mixing and cooking seem fairly simple, but it's a repetative and unforgiving task, and in the end you have to ship.
As a one-person exercise, it's fairly easy. But when you scale things up, it gets complicated. Several people working together cannot simply "make waffles". They have to coordinate and divide up the work. And to make waffles for a lot of people, you need multiple waffle irons, mixing stations, and serving.
The challenge for a team is how to organize themselves into assembly steps. At one station, some engineers melt the butter, crack eggs, and mix things. At the same time, another group prepares the dry ingredients, measuring properly. The output of the two streams mus
Thanks for watching my talk, Domain-Driven Desire at Øredev 2016. Here's a list of resources that inspired me, and will hopefully inspire you:
Note: This is an opinionated guide. While it is most effective for on-site, the same pattern can work with remote candidates.
Interviewing is hard. It's not easy to find good people, and once you do, it's often difficult to find out what they can do and how they work. A badly-run interview can pass over a great engineer. Conversely, some engineers are good at passing traditional tech interviews, but bring major problems with work habits or team fit.
The first priority of any manager is to hire the best people. Everything else must wait.
These are the Kickstarter Engineering and Data role definitions for both teams.
import code; code.interact(local=dict(globals(), **locals())) |