Explore >> Select a destination
|
You are here 
|
mariocarrion.com | ||
| | | | |
www.alfredo.motta.name
|
|
| | | | | [AI summary] Alfredo Motta promotes coding workshops in London for Ruby, Ruby on Rails, and JavaScript, emphasizing hands-on learning and community engagement. | |
| | | | |
www.byjp.me
|
|
| | | | | github.com Ruby-DLC is now available on github, and consequently as a gem! You can install with1: gem sources -a https://gems.github.com sudo gem install jphastings-dlc There's a gist explaining how to use the library and the rdoc documentation is still available on my project page. Please file an issue if you have any problems with the code, I haven't checked it thoroughly! Import note: This syntax is incorrect today, and the code only supports Ruby 1.x, so you'll have to make your own way if you're interested in using this!?? | |
| | | | |
mitrapunk.com
|
|
| | | | | The SPOT, or Single Point of Truth, principle is a better and more semantically-focused interpretation of DRY (Don't Repeat Yourself) | |
| | | | |
jonathan-frere.com
|
|
| | | This review is largely in response to the article "It's probably time to stop recommending Clean Code", and the ensuing Reddit discussion. A lot of really interesting points were brought up, but the big question that the author themself wasn't able to answer was: "What should we recommend instead?" I believe the book we should be recommending is A Philosophy of Software Design by John Ousterhout. In this post I want to spend a bit of time reviewing it and giving an overview of the contents, and then I want to explain why, in my opinion, it is such a good recommendation. | ||
