A full Go series for devs who already code in another language. From types and goroutines to a REST API in Docker.
Every dev landing in Go goes through the same two phases: first “am I seriously writing if err != nil every three lines?” and then, a few months later, “ok, now I get why”. This Go error handling article exists to shorten the trip between the two. Errors are values Go has no exceptions flying […]
READ MOREEvery dev landing in Go goes through the same two phases: first “am I seriously writing if err != nil every three lines?” and then, a few months later, “ok, now I get why”. This Go error handling article exists to shorten the trip between the two. Errors are values Go has no exceptions flying […]
READ MOREEvery dev landing in Go goes through the same two phases: first “am I seriously writing if err != nil every three lines?” and then, a few months later, “ok, now I get why”. This Go error handling article exists to shorten the trip between the two. Errors are values Go has no exceptions flying […]
READ MOREEvery dev landing in Go goes through the same two phases: first “am I seriously writing if err != nil every three lines?” and then, a few months later, “ok, now I get why”. This Go error handling article exists to shorten the trip between the two. Errors are values Go has no exceptions flying […]
READ MOREEvery dev landing in Go goes through the same two phases: first “am I seriously writing if err != nil every three lines?” and then, a few months later, “ok, now I get why”. This Go error handling article exists to shorten the trip between the two. Errors are values Go has no exceptions flying […]
READ MOREEvery dev landing in Go goes through the same two phases: first “am I seriously writing if err != nil every three lines?” and then, a few months later, “ok, now I get why”. This Go error handling article exists to shorten the trip between the two. Errors are values Go has no exceptions flying […]
READ MOREEvery dev landing in Go goes through the same two phases: first “am I seriously writing if err != nil every three lines?” and then, a few months later, “ok, now I get why”. This Go error handling article exists to shorten the trip between the two. Errors are values Go has no exceptions flying […]
READ MOREEvery dev landing in Go goes through the same two phases: first “am I seriously writing if err != nil every three lines?” and then, a few months later, “ok, now I get why”. This Go error handling article exists to shorten the trip between the two. Errors are values Go has no exceptions flying […]
READ MOREEvery dev landing in Go goes through the same two phases: first “am I seriously writing if err != nil every three lines?” and then, a few months later, “ok, now I get why”. This Go error handling article exists to shorten the trip between the two. Errors are values Go has no exceptions flying […]
READ MORE