I'll just leave this here:
* Growing a Language, by Guy Steele
Talks that changed the way I think about programming
31–40 of 103 posts
Re: Talks that changed the way I think about programming
#32These 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 "hole-driven" development style originated in dependently typed languages such as Agda and Idris, which I imagine Matthew's video was inspired by. So if you want to experience it right now, go learn Agda and use agda-mode in emacs. (Probably something similar exists for Idris. I don't know whether Coq has a notion of "holes".)
Re: Talks that changed the way I think about programming
#33Earlier quoted context omitted.
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.
We used this mess of a library, which provides no clear interface and corrupts data https://github.com/johnbywater/eventsourcing
Re: Talks that changed the way I think about programming
#34These 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 "hole-driven" development style originated in dependently typed languages such as Agda and Idris, which I imagine Matthew's video was inspired by. So if you want to experience it right now, go learn Agda and use agda-mode in emacs. (Probably something similar exists for Idris. I don't know whether Coq has a notion of "holes".)
idris-mode for Emacs does similar tricks ( https://github.com/idris-hackers/idris-mode ) and I've heard it's very nice.
The Idris REPL itself can do hole-based programming too, which can then be dumped out to a file (:m to list holes, :p to prove a hole, :a to write proofs to disk) http://docs.idris-lang.org/en/latest/reference/repl.html
Re: Talks that changed the way I think about programming
#35I'll just leave this here: * Growing a Language, by Guy Steele https://www.youtube.com/watch?v=_ahvzDzKdB0
I loved that talk!
I especially loved the moment when I finally understood the point he's trying to make is applied to the writing of the very talk he's giving.
Re: Talks that changed the way I think about programming
#36Are the start times on these YouTube links deliberate? Some of these link to the middle of the video, and I'm not sure why.
Re: Talks that changed the way I think about programming
#37Earlier quoted context omitted.
Care to elaborate? We're having quite good experiences with it at the moment, but would like to learn from others.
We used this mess of a library, which provides no clear interface and corrupts data https://github.com/johnbywater/eventsourcing
I'll go out on a limb here and say it wasn't Event Sourcing that caused the problems.
Anything can be ^H^H^H^Hmessed up.
Re: Talks that changed the way I think about programming
#38He mentioned a lie of:
Code should be designed around a model of the world
but I didn't hear any reason why not to? The Key/Value pair being the only reason, but besides that being a optimization / preoptimization in high performance applications, is there any reason to not design code around a model of the world?
Seems to me it makes things easier to think about.
Re: Talks that changed the way I think about programming
#39Earlier quoted context omitted.
Care to elaborate? We're having quite good experiences with it at the moment, but would like to learn from others.
We used this mess of a library, which provides no clear interface and corrupts data https://github.com/johnbywater/eventsourcing
A faulty implementation doesn't necessarily invalidate the idea. I also strongly suggest looking into statically typed languages. Python is very poorly suited to working with data.
Re: Talks that changed the way I think about programming
#40He mentioned a lie of: Code should be designed around a model of the world but I didn't hear any reason why not to? The Key/Value pair being the only reason, but besides that being a optimization / preoptimization in high performance applications, is there any reason to not design code around a model of the world? Seems to me it makes things easier to think about.
Well, you could argue that Acton instead argues that the data should be designed around a model of the world, and the code around that data. Although I concede that sounds like a nitpick.