How does Go Routine work?

Mon, 06 Apr 2026 06:47:50 +0000

Hello, I'm Ganesh. I'm building git-lrc, an AI code reviewer that runs on every commit. It is free, unlimited, and source-available on Github. Star Us to help devs discover the project. Do give it a try and share your feedback for improving the product.

What is a Go Routine?

Go Routine is a lightweight thread managed by the Go Scheduler. Any thread created by the Go Runtime is handled by the Go Scheduler.

Go Scheduler is a part of the Go Runtime that manages the execution of Go Routines. It is responsible for scheduling the execution of Go Routines and managing the state of the Go Routines.

In Other Programming Languages, each thread has a stack size of 256 KB to 1 MB. But in Go, each thread has a stack size of 2 KB to 4 kb.

How Concurrency Different From Parallelism?

Concurrency

It is mostly software based.
Is the ability of a program to perform multiple tasks at the same time.
It Focuses on reducing the execution time of a program.
It is exececuting tasks in a most effient order the order is not specified it depends on the scheduler.

Parallelism

It is mostly hardware based.
It is the ability of a processor to execute multiple instructions at the same time.
It truly executes tasks in parallel.

How to create a Go Routine?

Every Go Program executes in a main go routine.

Other go routines are created using go keyword.

package main

import "fmt"

func main() {
    go say("hello")
    say("world")
}
func say(word string) {
    for i := 0; i < 5; i++ {
        time.Sleep(100 * time.Millisecond)
        fmt.Println(word)
    }
}

We can see that the output is not in order.

This is because the Go Scheduler is responsible for scheduling the execution of Go Routines and managing the state of the Go Routines.

We can't predict the output of the go routine.

Output:

gk@jarvis:~/exp/code/rd/go-exmaple$ go run main.go 
hello
world
world
hello
hello
world
world
hello
hello
world
gk@jarvis:~/exp/code/rd/go-exmaple$ go run main.go 
world
hello
hello
world
world
hello
hello
world
world

Conclusion

In Next Article, we will see how to work with unordered events.

Any feedback or contributors are welcome! It’s online, source-available, and ready for anyone to use.
⭐ Star it on GitHub: https://github.com/HexmosTech/git-lrc

Big ideas are everywhere, but real change comes from showing up when you said you would.

Mon, 11 Aug 2025 19:13:30 +0000

People talk a lot about big ideas, but the thing that actually changes outcomes is much smaller: showing up when you said you would. Whether it’s a 6 a.m. run or a product launch, execution is what earns trust and trust is what compounds.

A few months ago, I invested in a gym. One of my goals was to build a sense of community, so we started a Saturday morning running club. Six a.m., every week.

I’ve been a runner for years, but lately I’d been letting “too tired” and “too busy” win. The running club changed that. When you’ve promised people you’ll be there, you show up — even if your bed feels like it has diplomatic immunity. And when you do, you realise the showing up is the work. The enthusiasm fluctuates, sure, but that’s part of the game. Week by week, more people join. The momentum builds.

That same principle is at the core of my work as a software engineer. In tech, execution isn’t just about ticking boxes. It’s about delivering on what you said you would, because trust is currency. And when things don’t go to plan (which they often do, spectacularly), the next best thing to delivering is communicating early. Silence erodes trust faster than failure.

In both running and work, follow-through compounds. Each time you do what you said you’d do — or own up when you can’t — you build a reputation that opens doors. That reputation doesn’t come from big heroic sprints. It comes from the quiet, boring, unglamorous act of showing up.