Whether for internal use, or destined for open-source stardom, writing good packages with clean and clear APIs will greatly increase the chance that the code is used and reused. Explore best practices, goals, and idioms that help make beautiful packages. EVENT: Golang UK Conference 2017 SPEAKER: Mat Ryer PERMISSIONS: The original video was published with the Creative Commons Attribution license (reuse allowed). CREDITS: Original video source: 🤍🤍youtube.com/watch?v=cAWlv2SeQus
This was both entertaining and useful. Thank you
Someone needs to update the title of this video to how to talk for 4 minutes and say absolutely nothing.
"it's falling apart, ain't it now guys" hahahaha, and then he gets out of that quicksand just as fast. I wish I had this superpower.
If Ricky Gervais were a Go developer...
cmkKxNN7cs4&t=15m29s 15:29 I mean, Mat is doing his thing but - please, what? The sound attenuation doesn't do it any good and makes it more awkward than it should've :(
The noise gate is distracting
The Greet example is kind of a bad example, unless proper documented, the user might fall into traps by forgetting to set the value. A better example would be sync.Mutex, nobody needs to know the default values to use the mutex properly, and the documentation states "The zero value for a Mutex is an unlocked mutex", which makes sense and is what you would expect. "Hi %v" is not the behavior you'd expect, it could be "Hello %v", "Hi, %v", "Hola, %v", "Oi, %v" etc.
cmkKxNN7cs4&t=10m13s 10:13 as a hispanic myself, I hereby grant you permission to fake a hispanic accent.
I laughed out loud at the jokes.
Why is the sound limiter sound high. His voice cuts all the time. It's really ennoying to listen to
New language programming influenced by go and others.
you can set aliases to package imports, no need for redundecy in the path
> put test code in different package
yeah don't do that if you can help it
go is overcomplicated.it/ overcomplicated.it may simple compared to c.but it is too orthodox and zero helping if you come from a language like php,js or python
I appreciated the "avoid constructors" argument as someone who has recently started writing non-trivial Go code, but has been writing code for four decades, I've seen far too many instances where constructor functions are used even though a trivial literal would be acceptable. Far too many engineers are trying to "future proof" their interface where it (almost never) makes sense.
The sound is horrible
Awesome talk and apply's to every language