Created
May 11, 2012 01:24
-
-
Save teohm/2656926 to your computer and use it in GitHub Desktop.
Practicing Ruby TOC
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Volume 1 is more like normal book contents | |
| Issue 1.1: Ruby's method lookup path, Part 1 | |
| Issue 1.2: Ruby's method lookup path, Part 2 | |
| Issue 1.3: Writing Configurable Applications, Part 1 | |
| Issue 1.4: Writing Configurable Applications, Part 2 | |
| Issue 1.5: Testing Anti-patterns; Testing Private Methods | |
| Issue 1.6: Meditations on Bad and Good Code, Part 1 | |
| Issue 1.7: Meditations on Bad and Good Code, Part 2 | |
| Issue 1.8: Uses for Modules, Part 1 | |
| Issue 1.9: Uses for Modules, Part 2 | |
| Issue 1.10: Uses for Modules, Part 3 | |
| Issue 1.10.a: Addendum to Uses For Modules, Part 3 | |
| Issue 1.11: Uses for Modules, Part 4 | |
| Issue 1.12: Rapid Prototyping | |
| Issue 1.13: Obfuscations of Christmas Past | |
| Issue 1.14: Duck Typing in Practice, Part 1 | |
| Issue 1.15: Duck Typing in Practice, Part 2 | |
| Issue 1.16: Interesting Ruby Hackers | |
| Issue 1.17: Interesting Ruby Hacker-Writers | |
| Issue 1.18: Dirty Little Secrets about Testing | |
| Issue 1.19: Thoughts on Mocking, Part 1 | |
| Issue 1.20: Thoughts on Mocking, Part 2 | |
| Issue 1.21: How to practice, Part 1 | |
| Issue 1.22: How to practice, Part 2 | |
| Issue 1.23: SOLID Design Principles | |
| Issue 1.24: Connascence as a Software Design Metric | |
| Issue 1.25: Creational Design Patterns | |
| Issue 1.26: Structural Design Patterns | |
| Volume 2 seem more advanced and with best practices talk, i guess | |
| Issue 2.1: Ways to load code | |
| Issue 2.2: How to attack sticky problems | |
| Issue 2.3: A closure is a double edged sword | |
| Issue 2.4: Implementing Enumerable & Enumerator in Ruby | |
| Issue 2.5: Thoughts on regression testing | |
| Issue 2.6: Learning new things step-by-step | |
| Issue 2.7: "Unobtrusive Ruby" in Practice | |
| Issue 2.8: Ruby and the singleton pattern don't get along | |
| Issue 2.9: Building Unix-style command line applications | |
| Issue 2.10: From requirements discovery to release | |
| Issue 2.11: Domain specific API construction | |
| Issue 2.12: Working with binary file formats | |
| Issue 2.13: Designing business reporting applications | |
| Issue 2.14: Thoughts on "Arguments and Results", Part 1 | |
| Issue 2.15: Thoughts on "Arguments and Results", Part 2 | |
| Volume 3 | |
| Issue 3.1: The qualities of great software | |
| Issue 3.2: Patterns for building excellent examples | |
| Issue 3.3: Exploring the depths of a Turing tarpit | |
| Issue 3.4: Climbing the spiral staircase of refactoring | |
| Issue 3.5: Framework design and implementation, Part 1 | |
| Issue 3.6: Framework design and implementation, Part 2 | |
| Issue 3.7: Criteria for disciplined inheritance, Part 1 | |
| Issue 3.8: Criteria for disciplined inheritance, Part 2 | |
| Issue 3.9: Using games to practice domain modeling | |
| Issue 3.10: Lessons learned from coding in the danger zone | |
| Volume 4 | |
| Issue 4.1: What are the costs and benefits of TDD? | |
| Issue 4.2: From prototype to minimal product, part 1 | |
| Issue 4.3 ended up being a failed experiment | |
| Issue 4.4: A cheap counterfeit of Jekyll |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment