Ennovar Go Course Cirriculum

A three week (4 days per week) course over Go centered around web development. After completing this course you should have the tools and experience required to be able to build web applications and independently further develop your knowledge in Go web programming.

This course is geared towards people who already have experience programming in other languages.

• Week One
  • Day One: Simple Data Types, Pointers, and Conditional Flow
    • Making use of Go documentation and the fact that Go is written in Go.
    • Resources: This Repository, ArdanLabs Repository, DevICT Slack (join the #go channel), Gophers Slack (join the #golang-newbies channel), Effective Go a free "ebook" of sorts about Golang.
    • Go CLI (go run, go build, go get, gofmt, goimports)
    • /basics/data_types/basic.go
    • /basics/data_types/sizes.go
    • /basics/data_types/pointers.go
    • /basics/conditonal_flow/main.go
    • Create an application that declares a variable called myName in the global scope of the appropriate type for a name and declare another variable in the same space that is the appropriate type to be able to store an unsigned integer up to 255 and call it myInt. In the main function, initialize the two variables and declare and initialize a new variable called myBool and assign it the value false with values and perform various dummy if/else and switch statement operations on them to demonstrate a solid understanding of conditional flow in Go.
  • Day Two: Complex Data Types and Loops
    • /basics/data_types/slices.go
    • /basics/data_types/maps.go
    • /basics/loops/main.go
    • Create an application that loops through a map with indexes of type int and keys of type string slice. Populate the map with random data and create a for loop that loops through all of keys of the map as well as all of the keys of each slice within the map.
  • Day Three: Functions and Structures
    • /basics/functions/main.go
    • /basics/data_types/structures.go
    • Create an application that loops through a map[int][]user where the int denotes the group number that each slice, []user, is a part of. The map will contain static data, and user will be a struct that has the fields FirstName, LastName, and Age that use appropriate data types. Within the loop call a function attached to each user struct that prints the first name, last name, and age of a user in a formatted fashion.
  • Day Four: File and Folder Architecture within Go Projects, Naming Conventions, and Commenting Conventions
    • There are no serious given standards for folder and file architecture within Golang other than the following:
      • File names should be kept to one word when possible.
      • The closest parent directory to a file should have the same name as the package that the file is in.
    • It is mostly opinion, but within /basics/architecture/* there is a simple given format that will help a bit and can be scaled to large projects.
    • The standard for naming functions, variables, and constants is strictly camel-case. No hyphens or underscores.
    • The standards for naming packages and interfaces can be found here.
    • The standards for comments within your code for the purpose of having a healthy godoc can be found here.
    • /basics/architecture/*
    • Questions over conventions, commenting, and architecture.
    • Extra-curricular learning after week one: Todd McLeod's playlist on YouTube "Build Web Apps with Golang" (Start at video #4).
• Week Two
  • Day One: HTTP Protocol Basics
    • Google Slides over HTTP Protocol
    • /web/full_webserver_example/*
    • Questions over HTTP Protocol and /web/full_webserver_example/*
  • Day Two: Minimal Examples of Web-servers in Go
    • /web/minimal_examples/mux/default.go
    • /web/minimal_examples/mux/servemux.go
    • /web/minimal_examples/no-mux/main.go
    • /web/minimal_examples/server/main.go
    • Questions over Examples
    • Create a simple web server using the http.DefaultServeMux with at least two patterns.
  • Day Three: Using Templates to Render HTML Content
    • /web/templates_simple/*
    • Questions over the templating code
    • Create a web server with two routes that use templates. There is no need to make the templates look nice, just make it functional.
  • Day Four: Writing APIs alongside Templates
    • /web/templates_complex/*
    • Questions over APIs and serving static files with different routes
    • Answer the following questions in a text file:
      • (1) What is a multiplexer and what is the difference between the functions Handle and HandleFunc which are attached to the multiplexer struct?
      • (2) When using the http.DefaultServeMux what argument must be passed to the handler parameter of http.ListenAndServe or the "Handler" struct field of http.Server?
      • (3) What package handles templates for HTML files?
      • (4) How do you define a template name?
      • (5) How do you insert a template by name into a template?
      • (6) What are 4 common HTTP request methods?
      • (7) True or false: The response code can be written after the response body.
      • (8) Respectively, what do the json.Marshal and json.Unmarshal/json.Decoder.Decode functions do?
• Week Three
  • Day One: Interfacing with a Postgresql Database
    • /web/databases/postgres/*
    • Questions over interfacing with postgresql
  • Day Two:
    • Create an application utilizing postgresql that handles users. Make use of public and private templates depending on the login status of the user.
  • Day Three:
    • Continue day two.
  • Day Four: Interfacing with BoltDB (NoSQL)
    • /web/databases/boltdb/*
    • Questions over interfacing with BoltDB