► Join my Discord community for free education 👉 discord.com/invite/bDy8t4b3Rz ► Become a Patreon for exclusive tutorials👉 www.patreon.com/anthonygg_ ► Buy me a coffee 👉 donate.stripe.com/aEU2a6ayH2uCa3u4gg Intro needs to be: "things YOU need to know" instead of I need to know :P :P Thanks for watching

I appreciate that you increased the text size! I also like that you had a summary of topics that you covered in the 2nd window for reference. Excellent information, thanks.

One of, if not the, best channels about go and software dev out there. Thanks so much for your work!

Great video! This content is pure gold for both newcomers and also some experienced devs that forget what idiomatic Go really means 😀. Thanks and keep it up!

This video deserves more likes if you ask me, very invaluable tips! Thanks Anthony!

This very good. Please add more like this. And best practices. My favorite is the embedded interface.

This was a phenomenal video, keep up the great work, looking forward to joining the patreon

Thanks KZfaq recommendations that showed this awesome channel. I extremely like your content about Golang. Wait for every video, big fan

This is so much useful brother, will really help to write the right code from the day 1 ....Amazing u r !!

I love your sense of humor 😂

Lot of value again in this video, keep them going!

Love your videos. One of the most "stupid" things I've seen in a language was the convention of "Er" for interface. The C# version of just adding `I` in front is much simpler. `IStorage` instead of Storer. The "Er" simpler doesn't always work for some words.

Excellent and very valuable points. Thanks sir

Keep them coming, the best go tutor 👍

Thank you Anthony, these are really good tips. I really enjoy your videos, they are always simple, on point and explained thoroughly. Appreciate the effort and thought put into it.

Interesting, Must it is new for me. Thank you for sharing your Knowledge.

Awesome stuff thanks man. Agree with all these points. However, I don’t get the minimalist variable naming. I’m of the of the opinion that variable names should be as descriptive as possible

Sorry but I'm not going to use small variable names to conform to your norm. They are going to be as long as i feel necessary to make it VERY clear what the variable is used for. But thanks for the rest of the tip, good content.

Tks for the tips. Are really good ones, important and helpful. Ow, and simple. Like Go. 🎉

Awesome! Writing idiomatic code instead of idiotic code!

ok bro, you convinced me - i have subscribed!

You're awesome. Thanks.

"I'm so sorry Rubiest" I got there and laugh :p

I fcking love your videos man

"I'm sorry rubyists" hahaa I'm dead. As a Rubyist very reluctantly working in Go, this hit too deep.

Love it!!

Thanks a lot!

Ahh the whole Suit thing - we call it a "type Prefix" in our Org - agree its important!

You are so cool!

Thanks you 💘

Can I please know which VS code theme are you using? :) Btw great video!

Tnx.

Just curious about last part of the video - constructor. If you define one New method per package, then how you suggest to structure your models/entities? Each entity per package with its own method or all entities in one package ?

Hello, very nice video! I would love to hear how idiomatic comments are written. Are points appended to the end? In which tense are the written? e.g something like // writing to port // write to port Comments start with the name of the variable but whats the best form to write one e.g. for variable Amount in a struct bank // Amount is the amount of money is in the bank // Amount holds the money // Amount contains information about how much money is in the bank I'm pretty confused how to write clean comments. Same applies to errors errrors.New("failed to write to pipe") errors.new("writing pipe failed") errors.New("write pipe") Thank you very much:) Take care

awesome

the "handle" naming convention is new to me. Do you have any articles about it? i do not feel it for 100% Thanks in advance!

Pretty useful to know these but very subjective imo. I highly disagree with the single character naming conventions. To each their own

In regards to grouping, I still struggle on whether I should group my variables. I generally follow the rule of declaring variables right before they're used. That way others can readily see the variable near its point of use. I think I learned that from Clean Code or Pragmmatic Programmer. If not, then probably some Medium post. Either way, I do that for all languages I use.

Hey, I really can't find any example or reference about "Must"+ panic

This guy codes like he's playing Starcraft

what hits home hard are the comments on what is going on; 7 times out of 10 he's quoting the golang docs verbatim; huge deal; also the remaining 3 are probably experience talking; wow

Name your return values, especially if you're returning multiple things.

Could you please explain why are you using vscode but not neovim ?

20:00

Great video, thanks! Your pronunciation of idiomatic is not very idiomatic, though ;)

The information is great. For the presentation, I am irrationally irritated by the spastic cursor. I don't think it's just typing mistakes, though I do think you'd be well served to slow down your typing 20% and make no errors. I think the editor is doing some sort of intellisense checking, which makes the cursor hop around. If NOT, for god's sake stop doing that, yourself. This is driving me crazy and distracting from the otherwise high quality content.

Its a good list but at sole point your being nit picky. Like putting mutex above the thing you want to use it for. Just have descriptive variable names.

Wow, the interface "tip" is such a bad example of cargo cult programming. Effective go only says this kind of derived naming is common for interfaces having only one or two methods.

Jfc that "enum" is pure trash. Sort it out, go.