Wat (2012) [video]
destroyallsoftware.com
Wat (2012) [video]
1–10 of 29 posts
Re: Wat (2012) [video]
#2Discussed back then: https://news.ycombinator.com/item?id=3515845 (98 comments)
Re: Wat (2012) [video]
#3Re: Wat (2012) [video]
#4It also kind of cemented for me that weird edge cases don't actually matter in practice (in my experience), and that a language can have lots to make fun of while still being lovely to use.
Re: Wat (2012) [video]
#5The WAT talk was rhetorically nice because it managed to joke about weird corners of the language without going into ranty programmer mode, but opted for a more gentle style of bemused boggling. It also kind of cemented for me that weird edge cases don't actually matter in practice (in my experience), and that a language can have lots to make fun of while still being lovely to use.
Re: Wat (2012) [video]
#6Re: Wat (2012) [video]
#7His talk about "Boundaries" taught me one of the most illuminating concepts I've learned in my career, about separation of concerns, functional core & imperative shell, unit testing, etc., and radically changed the way I write code - the talk uses Ruby as an example, but can be applicable to any language under the sun.
In fact, watch all five of them, they all reach this outstanding level of being educational, interesting and funny at the same time.
Re: Wat (2012) [video]
#8As per HN Guidelines https://news.ycombinator.com/newsguidelines.html>, please don't editorialize titles.
Re: Wat (2012) [video]
#9WAT is classic and very funny, but I recommend all software engineers to watch all of Gary Bernhardt's talks on his website: https://www.destroyallsoftware.com/talks His talk about "Boundaries" taught me one of the most illuminating concepts I've learned in my career, about separation of concerns, functional core & imperative shell, unit testing, etc., and radically changed the way I write code - the talk uses Ruby a…
Re: Wat (2012) [video]
#10The WAT talk was rhetorically nice because it managed to joke about weird corners of the language without going into ranty programmer mode, but opted for a more gentle style of bemused boggling. It also kind of cemented for me that weird edge cases don't actually matter in practice (in my experience), and that a language can have lots to make fun of while still being lovely to use.
I had the exact opposite impression. Indeed, this stuff is the cause of so much that gets attributed to something else (e.g. JavaScript framework churn being attributed to culture).
The problems caused by these issues compound as you work your way up the stack.