Organizing your Go (Golang) project's folder structure can help improve code readability, maintainability, and scalability. While there is no one-size-fits-all structure, here's a common folder structure for a Go project:
project-root/
├── cmd/
│ ├── your-app-name/
│ │ ├── main.go # Application entry point
│ │ └── ... # Other application-specific files| package animal | |
| const ( | |
| AnimalDog = iota | |
| AnimalCat | |
| AnimalBear | |
| ) | |
| type Animal interface { | |
| Speak() string |
| #!/bin/bash | |
| demo () { | |
| project_name="" | |
| if [ $# -eq 0 ]; then | |
| project_name=$(cat /dev/urandom | tr -dc 'a-zA-Z0-9' | fold -w 6 | head -n 1) | |
| else | |
| if [[ ( $1 == "--help") || $1 == "-h" ]]; then | |
| cat << EOF |
| # high sierra | |
| sudo launchctl stop com.openssh.sshd | |
| sudo launchctl start com.openssh.sshd | |
| # latest | |
| sudo vim /etc/services # (update the port config for ssh and save) | |
| sudo launchctl unload /System/Library/LaunchDaemons/ssh.plist | |
| sudo launchctl load -w /System/Library/LaunchDaemons/ssh.plist |
QEMU requires brew in OSX, so we need to install brew first.
To install brew we need to have the developer tools enabled in our system. In order to install those tools, we have two options.
xcode-select --install
| package main | |
| import ( | |
| "runtime" | |
| "fmt" | |
| "time" | |
| ) | |
| func main() { | |
| // Print our starting memory usage (should be around 0mb) |
See how a minor change to your commit message style can make a difference.
git commit -m"<type>(<optional scope>): <description>" \ -m"<optional body>" \ -m"<optional footer>"
System: Debian/Ubuntu/Fedora. Might work for others as well.
As mentioned here, to update a go version you will first need to uninstall the original version.
To uninstall, delete the /usr/local/go directory by:
FWIW: I (@rondy) am not the creator of the content shared here, which is an excerpt from Edmond Lau's book. I simply copied and pasted it from another location and saved it as a personal note, before it gained popularity on news.ycombinator.com. Unfortunately, I cannot recall the exact origin of the original source, nor was I able to find the author's name, so I am can't provide the appropriate credits.
Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.