https://github.com/fivepoint-0/learning-golang
Tour of Go(lang) Repository
https://github.com/fivepoint-0/learning-golang
development documentation go golang google learning learning-by-doing
Last synced: 10 days ago
JSON representation
Tour of Go(lang) Repository
- Host: GitHub
- URL: https://github.com/fivepoint-0/learning-golang
- Owner: fivepoint-0
- Created: 2024-05-26T21:42:12.000Z (about 2 years ago)
- Default Branch: main
- Last Pushed: 2024-08-28T20:54:22.000Z (almost 2 years ago)
- Last Synced: 2025-11-17T06:09:29.573Z (7 months ago)
- Topics: development, documentation, go, golang, google, learning, learning-by-doing
- Language: Go
- Homepage:
- Size: 117 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Tour of Go Learnbook
This repository is now meant to be a reflection of the Tour of Go book available at [A Tour of Go](https://go.dev/tour)
You can fork the `main` branch if you want to use the Tour of Go Learnbook as a blank slate.
The main sections of the `Tour of Go` are reflected in the subfolder `tour_of_go/` in the root of this repository. Those sections are, in order:
1. `welcome/`
2. `basics/`
3. `flowcontrol/`
4. `moretypes/`
5. `methods/`
6. `generics/`
7. `concurrency/`
Each of the subsection folders within the main section folders each have their corresponding `README.md`
Not every `README.md` has the required knowledge to make an example in the `main.go` file next to the `README.md`. This is on purpose, partly because I'm lazy, and partly because researching the usage and topics around one of the subjects in the subfolders is part of every programming journey... Alright, I'm mostly lazy.
### Luke's preferences/opinions on learning Golang through the Tour of Go:
---
1. I try as much as I can to make something inside of the codebase without looking up information.
2. I look online to compare my examples with examples from others, to see what I think I did well and what I think I could improve on.
3. There are multiple ways to solve problems, and finding the balance between ease-of-use and efficiency is different for every programmer, and, even for one programmer, different between programming problems.