markdown guide

That's my case! I (probably) know how to write and to use, but now sure how to maximize the benefits of it. =/


Pointers took me some time to wrap my head around.

Also, coming from Ruby where interfaces are more of an implicit concept, having to define them explicitly in Go was frustrating at first.


Interesting, implicit concept like how you pass in a Ruby value and it runs methods that are expected to be there?


Yeah, the idea of duck typing, where as long as an object responds to certain methods and had certain values it can be replaced with any other object, no matter the type, that implements the same methods and properties, without that interface having to be explicitly defined anywhere.

When I was doing Ruby I used to love the flexibility that me, now I can't imagine how anyone can maintain that lol.


The basic concept of interfaces. I don't see a reason I would ever use them, yet I'm sure I should be using them. I've read multiple articles (dozens) and still don't understand how/when I should implement them.


Interfaces and channels. I still have to stop and think every time I go to use them.

Classic DEV Post from Feb 8

Life Can Be Tough, But We Are DAMN Good at What We Do!

We are problem solvers, thinkers, tinkers, and dreamers. Personal challenges, no matter how severe, can NEVER take that away

&y H. Golang profile image
Software engineer at Diffeo (prev MIT), organizer at Boston Golang, resident #sloth enthusiast at everywhere

Still don't have a account? You're welcome to lurk, but it's better to be part of the community.

Sign up now ❤️