Thanks for the post, it's always nice to see people contributing posts to the #go tag on DEV. If you're curious about organizing Go code I recommend you give Style guideline for Go packages a read. It briefly covers certain approachs to ogranising code that is idiomatic to Go.
Also take a look at how Go as a language itself organises code within the stdlib. I've learned quite a bit around how to structure Go code by looking at the language source.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks for the post, it's always nice to see people contributing posts to the #go tag on DEV. If you're curious about organizing Go code I recommend you give Style guideline for Go packages a read. It briefly covers certain approachs to ogranising code that is idiomatic to Go.
Also take a look at how Go as a language itself organises code within the stdlib. I've learned quite a bit around how to structure Go code by looking at the language source.