What’s the Golang Pareto for an Golang developer?

#go #development

A few days ago I read the post "What’s the VIM Pareto for an IT professional?" on reddit and it gave me the idea to ask exactly the same for Golang.

I am aware that many things depend on the developer's area of responsibility. The answer of a CLI/TUI developer looks different than someone who writes microservices or web applications or desktop applications. I would just be interested in your answer, maybe with a small addition of what you focus on developing.

Which modules of the standard library and additional libs do you think of or what from Golang roadmap belongs to the 20% of Golang to do 80% of the Golang dev's tasks in your opinion?

Thank you for your answer!

Top comments (4)

gokayburuc.dev • Apr 11

How to Teach Golang to New Developers: Start with the Magic

Eighty percent of Golang’s appeal lies in its high integration capacity with large-scale web projects and its efficient garbage collection. If I were creating a roadmap for new developers learning Golang, I wouldn't start with dry syntax or theory. Instead, I would begin by showing them the magic—the real-world impact Golang has in large-scale web development.

Give People a Goal, Not Just Advice

People don’t want advice—they want goals, outcomes, and benefits. Advice often feels abstract or disconnected. On the other hand, a clear goal provides direction.

Some people need a goal to get started. Others are motivated purely by profits and benefits. Either way, both groups are focused on results. That’s why it's crucial to show them the results first—what they can build, what problems they can solve, or what performance gains they can achieve.

Once you’ve shown them what’s possible, then you can explain the reasons and methods behind it. Start with inspiration. Then teach the technique.

gokayburuc.dev • Apr 11

And from a developer to a developer advice:

Write these notes here in dev.to as markdown articles using the series:
github.com/vbd/Fieldnotes

Show them the experience by adding photos, screenshots, ideas etc. Finding a 25 years experienced developer is very rare nowadays.Any of your words can give spark to the new devs ( they are not junior but less experienced developers. I hate word of junior. )