GopherCon India: Evolution of a Gopher

GopherCon India: Evolution of a Gopher

This was the opening keynote of gophercon.in.

After interviewing multiple members of the community I have identified some stages in the evolution of a Gopher. From the newcomer to the expert, this talk will give you hints and advice on how to identify them and how to become a more skilled member of the Go community.

D8e5d79ca42edc07693b9c1aacaa7e5e?s=128

Francesc Campoy Flores

February 20, 2015
Tweet

Transcript

  1. evolution of a gopher francesc

  2. about me - Developer Advocate for the Google Cloud Platform

    - Developer Programs Engineer for the Go team since 2012 - Lover of all programming languages - Instructor at Google @francesc github.com/campoy
  3. about this talk Inspired “evolution of a developer” by Raquel

    Velez (@rockbot)
  4. None
  5. 1. the newcomer the phases of evolution

  6. 1. the newcomer 2. the explorer the phases of evolution

  7. 1. the newcomer 2. the explorer 3. the builder the

    phases of evolution
  8. 1. the newcomer 2. the explorer 3. the builder 4.

    the expert the phases of evolution
  9. None
  10. None
  11. the newcomer First steps: - tutorials - workshops Concepts: -

    syntax - slices and maps - functions, types, and methods
  12. create small programs, toy projects main resources: - go tour

    - go playground - documentation - golang-nuts/slack/irc playing around
  13. None
  14. - write some small projects - still gets lost -

    many new things to learn - but knows where to find help and ask questions the explorer
  15. learning curve note: this is graphic is absolutely not scientific

    explorer
  16. Go is awesome, I can do everything! ”let me migrate

    this framework to Go” But to improve something we have to understand it first. the peak of inflated expectations
  17. inflated expectations lead to painful realizations

  18. But I miss X feature from Y language! Use the

    language as is and have fun. The standard library is very useful. the trough of disillusionment
  19. Try new things - go generate - Go on Android

    Fighting the disillusionment
  20. - parsing with go/ast - generation with text/template github.com/campoy/jsonenums jsonenums

  21. package painkiller //go:generate jsonenums -type=Pill type Pill int const (

    Placebo Pill = iota Aspirin Ibuprofen Paracetamol Acetaminophen = Paracetamol )
  22. var _PillValueToName = map[Pill]string{ Placebo: “Placebo”, Aspirin: “Aspirin”, ... }

    func (r Pill) MarshalJSON() ([]byte, error) { s, ok := _PillValueToName[r] if !ok { return nil, fmt.Errorf("invalid Pill: %d", r) } return json.Marshal(s) }
  23. None
  24. Challenges and competitions gophergala.com golang-challenge.com

  25. None
  26. Solve a problem you care about New problems lead to

    new questions And sometimes new solutions the builder
  27. contribute to an existing project - Go - Docker -

    Kubernetes - Many other: github.com/golang/go/wiki/Projects
  28. tooling things that matter when you build stuff - go

    get/build/install/run - go generate - govet - go test -race - gofmt, goimports, goreturns
  29. Before goimports func main() { fmt.Println(“hello”) }

  30. After goimports package main import “fmt” func main() { fmt.Println(“hello”)

    }
  31. Before goreturns package foo func count() (int, error) { if

    err := check(); err != nil { return err } return n, nil }
  32. After goreturns package foo func count() (int, error) { if

    err := check(); err != nil { return 0, err } return n, nil }
  33. code reviews

  34. Intent: - fix mistakes - uniformize code style - improve

    quality of software - improve developers’ skill code reviews
  35. coding culture spreads via code reviews

  36. Learning and teaching opportunity code reviews

  37. None
  38. the expert - specs - philosophy - recognition

  39. Go is “just” a tool As any other programming language

    - it can be very advanced - or hard to master but - it is the means to an end
  40. - Different points of view - Synergy between different languages

    - Idiomatic adaptation of idioms Why using just a tool?
  41. None
  42. share your knowledge: - write - talk - complain the

    advocate
  43. go-meetups.appspot.com

  44. Gophers of every level of experience - top down -

    help gophers learn - bottom up - make the community more welcoming the advocate
  45. None
  46. thanks @francesc