From Go Tour to Go by Example: My Real Journey Into Golang

Go Programming Update: From Go Tour to Go by Example

Hello again! How’s it going out there?

Here’s another update just for you.

✅ What’s Next After “A Tour of Go”?

After completing the Go Tour, I moved on to the next learning resource — Go by Example. It’s a practical, snippet-based guide that teaches Go through annotated code examples.

But before diving deep, I had to set up an IDE for actual development.

💻 Choosing an IDE: LiteIDE vs VSCode

There are many editors out there, but I narrowed it down to two major options:

• Go LiteIDE
• VS Code with Go extensions

I decided to start with Go LiteIDE to get a more native experience.

⚙️ Installing Go LiteIDE Wasn't So Easy

Installing LiteIDE wasn’t as straightforward as I expected. It took me several minutes and a few web searches to get it right.

I had to follow multiple setup steps, but eventually, it worked.
📌 Spoiler alert: I’ll be writing a separate post on how to install and set up LiteIDE for Go.

🧠 My Observations So Far

1. Go Strings Use Double Quotes Only

Unlike languages like JavaScript and Python, where both ' and " work, in Go, strings must be in double quotes (").
Single quotes (') are for runes, not strings.

2. if/else Syntax Must Be Properly Aligned

Go is strict about how you write if/else.
This will not work:

if 1 == 1 {
    // do something
}
else {
    // error: unexpected else
}

This is the correct way:

if 1 == 1 {
    // do something
} else {
    // now it's valid
}

3. Still No Section About Comments or String Concatenation

So far, I haven’t seen an example of how to:

• Add comments
• Concatenate strings

This suggests that Go expects some prior programming experience from its users. It’s not hand-holding like beginner-friendly languages.

4. Arrays vs Slices in Go

Here’s a simple example to show the difference:

array := [3]string{"j", "d", "d"}     // Array
slice := []string{"j", "d", "d"}      // Slice

An array has a fixed size specified inside the square brackets.
A slice doesn’t specify the size and is more flexible.
They look similar but behave differently.

🧵 Final Thoughts (For Today)

Go continues to be an outstanding language — clean, powerful, and strict.
It forces you to think like a low-level systems developer, even while giving you modern conveniences.

I’m still getting used to the syntax and structure, but every day I learn something new that surprises me.

Until the next update — keep learning, and stay curious. 👋🏽

Learning Go: My Honest Thoughts After Completing the Go Tour in 2 Days

Go Programming Update: Day 2 – The Weird, the Wonderful, and the “Why Though?”

Hello again, and thank you for taking a moment to read through.

I understand your time is valuable, so I’ll keep this brief going forward.

🧠 Yesterday Was... Interesting.

Yesterday was another opportunity to experience something brilliantly human: a programming language created by man — Go.

Now, here are a few things I’ve learned that made me pause and go, “Wait, what?”

"In Go, it's common to write methods that gracefully handle being called with a nil receiver."

But… look at this code:

package main

import "fmt"

type I interface {
    M()
}

type T struct {
    S string
}

func (t *T) M() {
    if t == nil {
        fmt.Println("<nil>")
        return
    }
    fmt.Println(t.S)
}

func main() {
    var i I

    var t *T
    t.S = ""
    i = t
    describe(i)
    i.M()

    i = &T{"hello"}
    describe(i)
    i.M()
}

func describe(i I) {
    fmt.Printf("(%v, %T)\n", i, i)
}

Output:

panic: runtime error: invalid memory address or nil pointer dereference

There's nothing “graceful” about that! 😅

But honestly, if I had seen this code a week ago, I could only understand maybe 30% of it. Go code feels more like advanced programming—almost in the league of low-level languages.

🧱 Constructors and NewSomething

Then I stumbled on this: image.NewRGBA.

That threw me off completely at first. Coming from PHP or JavaScript, I assumed New was part of the method name.

Turns out, New is a convention, not a keyword. The actual type is image.RGBA. Go uses NewTypeName() to return an initialized instance — like a constructor function.

🟰 nil Instead of null

Go doesn’t use null — it uses nil.

🚫 The Underscore _ Is Not Just a Placeholder

for _, v := range arr {
    // Do something with v only
}

_, ok := someFunc()

The underscore isn’t decorative — it literally means: “Ignore this.”

💡 Keep an Open Mind

If this is your first time learning Go, please… don’t get your hopes too high in the first few days.

You're going to say “Hmm, this is weird” more than once.

• No shorthand if statements — braces {} are required.
• No class keyword — methods are tied to types via receivers.
• No inheritance — Go favors composition.
• Go forces unused imports and variables to be removed — and that's a good thing.

🧬 Go Method Syntax

func (receiver Type) MethodName(arg ArgType) ReturnType {
    // ...
}

If you don’t have a receiver, it's just a function. With a receiver, it becomes a method.

🔠 Naming Conventions

Go uses PascalCase like this: ErrNegativeSqrt.

I’m used to camelCase and snake_case, so this is another learning curve.

🧠 Old Habits Die Hard

I still find myself:

• Using () in if statements
• Ending lines with ;
• Trying to destructure like it’s JavaScript 😅

But that’s okay — it’s part of the learning curve.

🎉 I Completed the Tour of Go!

In just 2 days, I finished the official Go Tour tutorials! 🎉

I’m proud of this progress. It’s a strong start, and I’m beginning to appreciate the beauty and simplicity Go aims for — even if it’s not always obvious at first.

💙 Onward and Deeper

Next, I’ll dive into more advanced Go concepts: goroutines, channels, error handling, map, struct, slice and possibly building an API.

Until my next update, stay safe and stay healthy.