Rich Hickey • 3 years ago
Sorry, I have to disagree with the entire premise here.
A wide variety of experiences might lead to well-roundedness, but not to greatness, nor even goodness. By constantly switching from one thing to another you are always reaching above your comfort zone, yes, but doing so by resetting your skill and knowledge level to zero.
Mastery comes from a combination of at least several of the following:
| (ns com.x.aleph-test | |
| (require [aleph.http :as http] | |
| [manifold.deferred :as d] | |
| [manifold.stream :as s] | |
| [compojure.core :only [routes ANY GET PUT POST] :as compojure] | |
| [compojure.handler :as handler] | |
| [clj-http.client :as http-client] | |
| )) | |
| (comment |
The best way to learn and master iOS development is to read the official documentation. It can be boring but you can trust its accuracy and the information will be presented without opinion.
Read documents in order where indicated.
| TCP Connection States | |
| Following is a brief explanation of this handshake. In this context the "client" is the peer requesting a connection and the "server" is the peer accepting a connection. Note that this notation does not reflect Client/Server relationships as an architectural principal. | |
| Connection Establishment | |
| The client sends a SYN message which contains the server's port and the client's Initial Sequence Number (ISN) to the server (active open). | |
| The server sends back its own SYN and ACK (which consists of the client's ISN + 1). | |
| The Client sends an ACK (which consists of the server's ISN + 1). |
| (ns virgil | |
| (:require | |
| [clojure.java.io :as io] | |
| [clojure.string :as str] | |
| [filevents.core :as fe]) | |
| (:import | |
| [javax.tools | |
| DiagnosticCollector | |
| ForwardingJavaFileManager | |
| JavaCompiler |
| (ns names | |
| (:refer-clojure :exclude [name]) | |
| (:use nq.core)) | |
| (defmacro ? [xs] | |
| `(rand-nth ~xs)) | |
| (defn stitch [xs] | |
| (->> xs | |
| flatten |
| package main | |
| import ( | |
| "fmt" | |
| "os" | |
| "os/exec" | |
| "syscall" | |
| ) | |
| func main() { |
| #!/bin/bash | |
| # Go build script that runs cloc, cpd, lint, vet, test and coverage for Jenkins | |
| # | |
| # Outside tools include: | |
| # gocov: go get github.com/axw/gocov | |
| # gocov-xml: go get github.com/t-yuki/gocov-xml | |
| # go2xunit: go get bitbucket.org/tebeka/go2xunit | |
| # jscpd: npm i jscpd -g | |
| # cloc: npm i cloc -g |
The consensus protocol limits on blocks are:
1 million or fewer bytes canonically-serialized size. 20,000 or fewer "sigops"
Unfortunately, Satoshi implemented those as quick fixes with zero code review and little testing (Bitcoin was not a Big Deal back then, it was the right decision at the time), and the way sigop counting is done is... well, just wrong.
Here's how Satoshi did it, as pseudo-code (see GetLegacySigOpCount in main.cpp for actual code):
For all the transactions in a block:
