Thanks for sharing.
Talks that changed the way I think about programming
21–30 of 103 posts
Re: Talks that changed the way I think about programming
#22I always hugely enjoy these lists, thanks for sharing this one as well. Great material in there :-)
Re: Talks that changed the way I think about programming
#23I love this quote from Eskill's talk
"C++ is evil because it makes dumb people think they are clever."
Replace C++ with any "intelligent" framework or language.
Re: Talks that changed the way I think about programming
#24> Iterating over a two dimensional array by row is much faster than by column. Another fun fact is staggering array accesses is faster then linear acesses.
I wonder if this is language or even compiler dependent. Are there things that transpose memory organization? I for one always get confused which index is the row and which is the column when coding. Every damn time I've done a 2D iteration in the last 15+ years. Is it [col][row] or [row][col] ... I imagine it depends.
I'm not alone!!!!!! :) I was having brain melting with today's http://adventofcode.com/2016/day/8 I'm attempting everything in Elixir and it's quite different from what I'm used to!
Re: Talks that changed the way I think about programming
#25I just watched the Blow talk. I had never seen him talk before and was really impressed by his perspective. I found myself agreeing with many of his points in a way that I never would have a couple years ago. I love how his main metric for optimization is developer time more than anything. I've learned how important this is in recent years.
Re: Talks that changed the way I think about programming
#26I suspect a lot of these video are the most powerful when you encounter them at exactly the time you happen to be wrestling with those same ideas yourself.
Every time I design software, I'm think back to Gary Bernhardt's "Boundaries" talk¹ and his practical, concrete suggestions for writing testable code. But I've never met anybody else who seemed as impressed as I was by the idea.
Re: Talks that changed the way I think about programming
#27These talks are a little skewed to the game/high performance programming side of the art, but still very interesting in general. Of the ones I've already seen I really like Mike Acton's talk.
Since this has become such a nice thread some additions I'd add:
* Sandi Metz going through the Gilded Rose or "All the small things"
https://www.youtube.com/watch?v=8bZh5LMaSmE
I already subscribed to her programming style and the general Ruby TDD/BDD movement, but this talk captures all the important values in a single example. I think it made my programming style no longer based on vague things like experience or intuition, but just on concrete merit shown in this talk.
* Matthew Brecknell demonstrating Hole Driven Development
https://www.youtube.com/watch?v=52VsgyexS8Q
The programming style demonstrated in this video is a real mind bender. I think most Haskell programmers use a weaker version of this, Matthew takes it to the extreme. I didn't adapt this style, I don't think it's practical, but it's the sort of thing that some person someday will incorporate in some more comfortable way in a new language or platform as a revolutionary feature.
Re: Talks that changed the way I think about programming
#28The following talk about event sourcing (not listed in the article)•, really made an impact on me: Event Sourcing - Greg Young https://www.youtube.com/watch?v=JHGkaShoyNs •: Not that I really expected it to be I guess.
Overly complicated pointless eventsourcing wasted 1mil+ at my previous employer. Now they have to spend 6 months removing it all.
Re: Talks that changed the way I think about programming
#29These two made an impression on me, especially regarding the delicate trade off between implicit and explicit.
Among other things, how and why to making things more implicit:
http://youtube.com/watch?v=wf-BqAjZb8M (Beyond PEP8 by Raymond Hettinger)
When implicit goes too far:
https://www.destroyallsoftware.com/talks/wat (wat by Gary Bernhardt)
Re: Talks that changed the way I think about programming
#30The following talk about event sourcing (not listed in the article)•, really made an impact on me: Event Sourcing - Greg Young https://www.youtube.com/watch?v=JHGkaShoyNs •: Not that I really expected it to be I guess.
Overly complicated pointless eventsourcing wasted 1mil+ at my previous employer. Now they have to spend 6 months removing it all.
Care to elaborate? We're having quite good experiences with it at the moment, but would like to learn from others.