Go Programming Interview Questions: Mastering Short Declaration Operators

✅LEARN THE GO PROGRAMMING LANGUAGE - FULL COURSE

This video specifically focuses on the 'Short Declaration Operator', a key concept that could make or break your interview. This operator is used widely in idiomatic Go code, hence its understanding can reflect your proficiency in the language -- insights into when to use it and how it differentiates from the 'var' declaration, along with its usage inside and outside of function bodies. The video also revisits the concept of 'Idiomatic Go Code' from a previous video.

✅LEARN THE GO PROGRAMMING LANGUAGE - FULL COURSE

😃the github repo:
look in the "000-bm-interview-questions" folder 😃

[lanreuzamere]

Well done Sir! GOD Bless you greatly 🙏

[RichM]

When it comes to idiomatic go code I think we've got a problem with nested functions. I see this all the time when looking at code on github (Not that my code is clean by any means!) When a program or package branches main - >func1 - > func2 - > func3 - > func4 - > func5 - > func6 all of these functions are open, waiting for a return, and like nested conditionals -- becomes really hard to follow. Then what really doesn't make sense is each function is four lines long, and your IDE tells you each function is only used once. Why not make it all a part of the same function? I typically don't like to go one or two levels before returning back to main. And if it's only used once and only four lines long -- keep it in the same function. It seems like everyone is too afraid of being a spaghetti coder, but becoming overly functional can be just as bad. Functions should have a purpose.