[tptacek]

Yes. Nobody here wants to learn how Brad Fitzpatrick reasons about, designs, and implements server software. It's all spam.

[drhayes9]

Second this. One of my favorite things is getting a slice, however small, of how truly great programmers get their work done, why they chose what they did, and what the results were.

We actually need more of this on HN, not less.

[ballard]

This doesn't reveal any secrets into systems engineering, but it slices:

    package main

    import "fmt"
    
    func main() {
        cake := make([]byte, 2600)
        copy(cake, []byte("Happy Birthday, Lundberg !"))
        lundberg := cake[:8]
        milton := cake[:0]
        fmt.Println("Lundberg got :", string(lundberg))
        fmt.Println("Milton got :", string(milton))
    }

    // :-)  (Ran out of UTF8 smileys and movie fact checkers).
    // And yes could've used string but bytes are awesomer.

[pjmlp]

Slices aren't Go specific.

[ballard]

Browsing the go goog client source is 30% of it. Go and others could use screencasts of how they fixed production problems, regardless of what lawyers, job security worriers or "hide the dust" folks would say. Mindset is best communicated by solving something real.

http://code.google.com/p/google-api-go-client/source/checkou...