#Go Lang Mentor Needed
1 messages · Page 1 of 1 (latest)
@bitter pasture I was scrolling through the members, and I saw moderator Rain knows Go, can I ping her here if its possible?
Hey @eternal junco 😄 If you're free to chat some time, Akashjeet was hoping to speak to you about Go
Thanks a lot!
Hey, what's up? While I'm not gonna be a mentor, if you have some specific questions about the language, I'd be okay to answer!
Hey @eternal junco , thanks for jumping in and I totally respect the mentoring boundary.
Basically, I’m wrapping up my exams soon and shifting gears entirely toward GSoC 2027. I have a background in Java and Python, but I'm moving toward backend and cloud, which is why I want to learn Go (as its the go to lang for GSoC). My biggest hurdle right now is figuring out how to bridge the gap between just "learning syntax" and actually making meaningful open-source contributions. Coming from Java/Python, what kind of Go projects actually stand out for GSoC?
If you have the time, I'd love to know what kind of projects or deep-dive concepts you think actually prepare someone to tackle a large Go codebase.
If I opt for a Go mentor who may help me for clearing GSoC, will I find them in this server? Do you know anyone who helps contributors? If no then not a problem!
Any good materials or sites I can learn Go from?
Any advice to point me in the right direction would be awesome!
Sorry for such a long message, I tried to keep it less but this is as less as I could trim it 😭😭✨
Hmm, I never took part in GSoC myself, so I can’t speak to what kind of projects do well for it specifically. I think though that any language would do as GSoC is not language based, so doesn’t have to be Golang. Python is incredibly popular too.
Go is relatively easy to pick up, it has a very small number of keywords compared to other languages, so coming from Java or Python, the syntax will click pretty quickly.
Once you know the syntax, you can already start making meaningful open source contributions. Not every PR needs to be perfect. If you contribute to projects, people will often just point out what’s off and you can fix it from there. It’s always good to read a project’s contributing guide and filter issues by “help wanted” or sometimes by “good first issue” if project has such. Every project has its own conventions though and way of doing things, but you may learn that from generally looking through project, it’s readme and other md files you find.
The only materials I personally used were:
https://go.dev/tour/welcome/1
https://gobyexample.com
The rest is best to learn by doing in my view.
I don’t know any mentors to point you toward 🙏
Makes total sense. I definitely needed to hear that not every PR has to be perfect right out of the gate. Those two links look exactly like what I need to start with. Thanks for the solid advice and for pointing me in the right direction! ✨