☀️🌴 The Ultimate Go Tour #4 ❤️ Design Guidelines & Code Reviews

[@ekeminios]

Thank you Todd

[@toddmcleod-learn-to-code]

Yes! Thank you for the comment! How is you Go journey coming?

[@ekeminios]

@@toddmcleod-learn-to-code You're welcome! It's been going fine - taking a Go specialization course on Coursera

[@mysteryforhad]

That's awesome.

[@toddmcleod-learn-to-code]

I'm glad you like it, Forhad! Thank you!!

[@RichM1967]

One of my largest concerns for design is nesting. Nesting with for loops, if else if, switch statements. When I see at the end of a chunk of code five levels of curly braces -- I need to simplify that. Another is nested functions. I've seen go code where the author has you going down a rabbit hole of functions calling other functions, those functions are in different files, and each of those functions are only five to ten lines, and are only used once... If it's only used once - why create a new function? Very hard to follow that code. It seems like they think there is a size limit, that a function that has more than 10 lines in it is bad.

[@toddmcleod-learn-to-code]

Yes, great comment. I'm going to add this to the "code review check" in the notes

[@toddmcleod-learn-to-code]

github.com/GoesToEleven/learn-to-code-go-version-03/tree/main/000-br-bk-go-tour/02c-design-guides