some moar content

This commit is contained in:
Mark McGranaghan 2012-09-17 17:46:15 -07:00
parent d4f22d4bec
commit 1acd30143c
7 changed files with 63 additions and 23 deletions

42
README
View File

@ -1,3 +1,9 @@
= values
design
curation
excellence
excitement
= validation = validation
private emails private emails
@gobyexample twitter followers, retweets @gobyexample twitter followers, retweets
@ -5,23 +11,17 @@ blog posts: views, comments, hn score, hn comments
gobyexample.com signups gobyexample.com signups
= distribution = distribution
* leading blog posts * blog
* a new kind of programming book
* programmers learn by examples - minimize text, maximize code
* programmers want to ship software - focus on working programs, toolchain
* design matters - syntax highlighting, typography
* marketing matters - twitter,
* select, actors, threads, and event loops
* small go programming examples
* newsletter * newsletter
* twitter * twitter
* stack overflow answers * stack overflow answers
* web site
* free books for contributors and reviewers
= pricing = pricing
* high * $39
* updates * updates forever
* no drm * no drm
* offers of free books in comments
= source = source
* popular github libraries * popular github libraries
@ -30,16 +30,10 @@ gobyexample.com signups
* handbook format * handbook format
* rosetta stone * rosetta stone
* building an actual fucking app * building an actual fucking app
* versioned transitive libraries and pegging
* creating and distributing packages, putting on github
* distributing go binary programs
* deploying to heroku
* sort-by
* errors
* compilation
* ruby and nodejs stdlib * ruby and nodejs stdlib
* ruby and nodejs killer apps * ruby and nodejs killer apps
= topics
* gzip * gzip
* sending email * sending email
* listing files * listing files
@ -70,8 +64,10 @@ gobyexample.com signups
* tty * tty
* iota * iota
* apps with multiple named binaries * apps with multiple named binaries
* versioned transitive libraries and pegging
http://code.google.com/p/go-wiki/wiki/GithubCodeLayout * creating and distributing packages, putting on github
http://code.google.com/p/go-wiki/wiki/PackagePublishing * distributing go binary programs
http://blog.golang.org/2012/08/organizing-go-code.html * deploying to heroku
http://golang.org/doc/code.html * sort-by
* errors
* compilation

View File

@ -0,0 +1,9 @@
## Go by Example: a Book for Hackers
* a new kind of programming book
* programmers learn by examples - minimize text, maximize code
* programmers want to ship software - focus on working programs, toolchain
* design matters - syntax highlighting, typography
* marketing matters - twitter,
* select, actors, threads, and event loops
* small go programming examples

View File

@ -0,0 +1,3 @@
very common: fetch json document, parse into in-memory data structure
how this can be not terrible

11
blog/go-on-heroku.md Normal file
View File

@ -0,0 +1,11 @@
## Go on Heroku
Base on quickstart.
#### Calls to Action
...
Do you want to learn more about Go? I'm writing a book about how to ship Go code. Sign up at gobyexample.com for updates.
...

View File

@ -0,0 +1,13 @@
## Go Package Versioning and Management
Trick question.
Do not change public APIs.
The vendored option.
Every major programming language has evolved.
#### Call to Action
Want to learn more about go. [Go by Example]() will teach you!

View File

@ -0,0 +1 @@
* toolchain used to build the book, perhaps test code samples

View File

@ -0,0 +1,7 @@
system-mediated concurrency
a mechanism for participation
find that fucking old gist
erlang and go strictly more powerful, but potentially harder to understand