406 karma · joined August 4, 2010
Or at least your monkeypatches!
Longer writeup is at https://thomasleecopeland.com/2015/08/06/running-rails-updat... - it's 3+ years old now, but, hey.
http://www.benning.army.mil/armor/316thCav/ASA/content/pdf/A...
Focus on strong object oriented programming
What I've learned from Ruby is to favor functional programming concepts - minimize side effects, isolate state mutation, etc. Ruby is definitely OO, but when my Ruby code is more functional it's less buggy, easier to understand and move around, and generally less convoluted.https://www.ruby-lang.org/en/news/2017/10/10/ruby-2-5-0-prev...
And so it did! https://en.wikipedia.org/wiki/YARV
And if you're standing that watch that means you're not standing port and starboard (i.e. 4 hours on 4 hours off) so, could be worse!
More generally I get worried about my ActiveRecord objects getting too bulky and business logic getting all wound up in post-transition callbacks and such. But that's something that can be managed with service objects and being disciplined about triggering state changes.
https://www.functionalgeekery.com/
There's at least one episode that's devoted to Idris:
https://thomasleecopeland.com/2014/10/22/finding-suboptimal-...
I haven't worked on it much recently though because the problems it found weren't that significant. But I like the idea of runtime analysis for finding issues, especially in a dynamically-typed language.
https://militaryreadinglists.com/books/1191-infantry-attacks
It's using the English "Infantry Attacks" translated title though as you can see.
The really nice thing is that since many of those lists are refreshed yearly, they are an ongoing fountain of interesting books. Good stuff!