You reiterate my question in the second sentence: How do we weight these different privileges?
1,010 karma · joined June 5, 2012
You reiterate my question in the second sentence: How do we weight these different privileges?
I never claimed IQ was the best measure (surprised it looked like random noise though), but certainly our cognitive traits matter. So to my question: How do you distinguish that privilege from the privilege you got from your "class"?
Edit: Sorry if I came across snarky here, I appreciate your answer!
Does privilege imply that you got it from your "class"? This seems like a classic nature/nurture fallacy.
Then, for a small subset of data, I manually verified that all results were correct.
Where’s your test suite man? :)This debate totally changed the way I look at Assange. So no, I don't have to defend him.
Here's a 34 line implementation I use on a node production system. It writes struct-like JavaScript objects that represents events to disk. When reading it back I do a fold (or .reduce) to build the state.
And yes –– it could be way smarter (writing to memory and disk), but YAGNI has been working out pretty well so far.
class EventStore {
constructor(file) {
this.file = file;
this.cache = null;
}
async appendEvent(event) {
// Purge the cache for entries since we mutated the store.
this.cache = null;
return new Promise((resolve, reject) => {
createWriteStream(this.file, { flags: 'a' })
.on('error', reject)
.on('close', resolve)
.end(`${JSON.stringify(event)}\n`);
});
}
async readEvents() {
if (this.cache !== null) {
return this.cache;
}
try {
const data = await readFile(this.file, 'utf-8');
const lines = data.split('\n').filter(line => line);
const events = lines.map(line => JSON.parse(line));
this.cache = events;
return events;
} catch (error) {
return [];
}
}
}This made it possible to hijack other accounts, including our professors'. So we hacked our own grades and then reported it.
Blog post here: https://bustbyte.no/blog/how-we-hacked-blackboard-and-change...
File transfer between machines:
$ nc -l 1234 > filename.out
Using a second machine, connect to the listening nc process, feeding it the file which is to be transferred: $ nc host.example.com 1234 < filename.in
Or a simple web server: $ while true ; do nc -l -p 1500 -c 'echo -e "HTTP/1.1 200 OK\n\n $(date)"'; done[1] https://github.com/vespene-io/vespene/blob/master/vespene/mo...
Types just smuggle themselves in with the rest of the program (granted they only cover a subset of the bugs tests do).
Fewer pieces of the puzzle will let you quickly identify bottlenecks, instead of trying to anticipate them before everything breaks.