In this episode, David and Craig discuss Smalltalk coding style.
https://s3.amazonaws.com/smalltalkreflections/SmalltalkReflections_014.mp3
Items mentioned in this podcast
ESUG http://www.esug.org/wiki/pier/Conferences/2015
Camp Smalltalk Ottawa http://www.simberon.com/campsmalltalkottawa2015/
Camp Smalltalk Portland http://esug.org/wiki/pier/About/ESUGblog/2015-05-07
Pharo 4 http://pharo.org/news/pharo-4.0-released
Pharo Coding Sprint at ECOOP http://2015.ecoop.org/track/Pharo-2015
Chip computer https://www.kickstarter.com/projects/1598272670/chip-the-worlds-first-9-computer?ref=nav_search
Shout on Squeak http://map.squeak.org/package/e5c1aec2-0eb9-492d-8cb1-44f64c5b631a
The Smalltalk Jobs Report can be found here:
https://smalltalkjobs.wordpress.com/author/jsavidge/
I started using [ :_ | _ doSomething: param ] in my VW code because I'm used to using _ in pattern matching code to mean 'don't care' (in the many languages that support destructuring). It means I don't have to cognitively deal with a parameter name. I'd prefer the even more concise (and not uncommon) anonymous block params e.g. [ %1 doSomething: param ]. Heresy!
ReplyDeleteBTW: I think your ducking should be more aggressive, preferably to silence :) It's quite difficult to understand the speech during your intros/outros.