nil is not always nil.

#Tweet by inanc
➖➖➖➖➖➖➖➖➖
🕊 @gopher_academy

✅ When to use what?

Go ↓
Infrastructural programming and servers. Less is more. Simplicity.

Rust ↓
Resource-constrained environments. Every byte and CPU cycle matters. Safety is critical. Can’t say simple.

Pick your poison ☠️ 😂

#Tweet by inanc
➖➖➖➖➖➖➖➖➖
🕊 @gopher_academy

In Go, everything is passed by value. Even pointers.

#Tweet by inanc
➖➖➖➖➖➖➖➖➖
🕊 @gopher_academy

🔥 Go is unconventional yet versatile.

🔥 Go isn't just OOP, functional, or procedural.

🚀 It's a unique blend of all and beyond.

✅ If you aim for idiomatic code, don't confine it to any one style.

#Tweet by inanc
➖➖➖➖➖➖➖➖➖
🕊 @gopher_academy

In golang, we "expect" errors, but we don't "expect" panics.

😊 Errors are our sane behavior
😱 Panics are our manic behavior

#Tweet by inanc
➖➖➖➖➖➖➖➖➖
🕊 @gopher_academy

100% test coverage != bug-free🪳

#Tweet by inanc
➖➖➖➖➖➖➖➖➖
🕊 @gopher_academy

A few golang tips for writing effective Go code:

1. Make it easy to read from top to bottom
2. Do not hide the cost of doing something
3. Do not prematurely abstract

These are not rules, just advice.

#Tweet by inanc
➖➖➖➖➖➖➖➖➖
🕊 @gopher_academy

🚀 golang Optimization Tip:

Convert string to []byte without allocation.

Only do this in a hot spot after careful consideration.

#Tweet by inanc
➖➖➖➖➖➖➖➖➖
🕊 @gopher_academy

🚀 golang Optimization Tip:

Convert []byte to string without allocation.

Only do this in a hot spot after careful consideration.

#Tweet by inanc
➖➖➖➖➖➖➖➖➖
🕊 @gopher_academy

✅ An error message better not contain:

failed,
cannot,
can't, ...

It's an error already + you hurt chained err output:

failed to open:
failed to connect:
failed to fly: ...

Instead, do

opening:
connecting:
flying: no wings exist.

#Tweet by inanc
➖➖➖➖➖➖➖➖➖
🕊 @gopher_academy