| { | |
| "shot": { | |
| "composition": "tracking shot behind skateboarder weaving through fortress market alleys, villagers and stalls rushing past", | |
| "lens": "handheld Steadicam with wide-angle medieval texture emphasis", | |
| "frame_rate": "96fps with intermittent speed ramps", | |
| "camera_movement": "fluid gliding pan following skateboarder, sudden whip-pans to capture near-collisions" | |
| }, | |
| "subject": { | |
| "description": "a young Tamil woman skillfully skateboarding, crouching low to accelerate and kick-turn between narrow market passages", | |
| "wardrobe": "simple medieval tunic with practical wrap for mobility", |
| { | |
| "shot": { | |
| "composition": "POV from kart cockpit, hands gripping steering wheel tightly, mall corridors stretching ahead at high speed", | |
| "lens": "GoPro ultra-wide dynamic lens", | |
| "frame_rate": "120fps with speed-ramped slow motion bursts", | |
| "camera_movement": "fast forward rush with rapid swerves, head-bob tracking turns" | |
| }, | |
| "subject": { | |
| "description": "driver’s hands steering violently as kart races through rustic paddy terraces in Bali", | |
| "wardrobe": "racing gloves visible on wheel", |
These resources (articles, books, and videos) are useful when you're starting to learn the language, or when you're learning a specific part of the language. This an opinionated list, no doubt. I've compiled this list from writing and teaching Clojure over the last 10 years.
| Latency Comparison Numbers (~2012) | |
| ---------------------------------- | |
| L1 cache reference 0.5 ns | |
| Branch mispredict 5 ns | |
| L2 cache reference 7 ns 14x L1 cache | |
| Mutex lock/unlock 25 ns | |
| Main memory reference 100 ns 20x L2 cache, 200x L1 cache | |
| Compress 1K bytes with Zippy 3,000 ns 3 us | |
| Send 1K bytes over 1 Gbps network 10,000 ns 10 us | |
| Read 4K randomly from SSD* 150,000 ns 150 us ~1GB/sec SSD |
In order of first appearance in The Morning Paper.
The Linux kernel is written in C, so you should have at least a basic understanding of C before diving into kernel work. You don't need expert level C knowledge, since you can always pick some things up underway, but it certainly helps to know the language and to have written some userspace C programs already.
It will also help to be a Linux user. If you have never used Linux before, it's probably a good idea to download a distro and get comfortable with it before you start doing kernel work.
Lastly, knowing git is not actually required, but can really help you (since you can dig through changelogs and search for information you'll need). At a minimum you should probably be able to clone the git repository to a local directory.
| *C function* | |
| int fact(int n){ | |
| if (n <= 1) return 1; | |
| return n * fact(n-1); | |
| } | |
| -- | |
| *NASM code* | |
| default rel | |
| global _main | |
| section .data |
| //This uses char* pointers. The same thing can be done using character arrays as well. | |
| #include<stdio.h> | |
| #include<stdlib.h> | |
| void mystrcpy(char* first, char* second){ | |
| while(*first != '\0'){ | |
| *second = *first; | |
| first++; | |
| second++; | |
| } |
My notes from attempting to read the Dynamo paper ( Dynamo: Amazon's Highly Available Key-value Store)
Buzzwords: Key-Value store, primary key, eventual consistency, CAP theorem, hinted handoff, consistent hashing, virtual nodes.
