This is inspired by A half-hour to learn Rust and Zig in 30 minutes.
Your first Go program as a classical "Hello World" is pretty simple:
First we create a workspace for our project:
This is inspired by A half-hour to learn Rust and Zig in 30 minutes.
Your first Go program as a classical "Hello World" is pretty simple:
First we create a workspace for our project:
[alias] | |
wip = for-each-ref --sort='authordate:iso8601' --format=' %(color:green)%(authordate:relative)%09%(color:white)%(refname:short)' refs/heads | |
package logger | |
import ( | |
"fmt" | |
"path" | |
"runtime" | |
"github.com/sirupsen/logrus" | |
) |
This is a compiled list of falsehoods programmers tend to believe about working with time.
Don't re-invent a date time library yourself. If you think you understand everything about time, you're probably doing it wrong.
These are the Kickstarter Engineering and Data role definitions for both teams.
# find the IP addresses of many hosts on the network | |
# step 1. obtain the broadcast address from ifconfig | |
# step 2. ping the broadcast address | |
$ ifconfig -a | grep broadcast | |
inet 192.168.1.102 netmask 0xffffff00 broadcast 192.168.1.255 | |
inet 192.168.68.1 netmask 0xffffff00 broadcast 192.168.68.255 | |
inet 192.168.174.1 netmask 0xffffff00 broadcast 192.168.174.255 | |
$ ping 192.168.1.255 | |
PING 192.168.1.255 (192.168.1.255): 56 data bytes | |
64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=0.634 ms |