The DRY Principle

Rails Coach

Content provided by Charles Max Wood. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Charles Max Wood or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

13y ago 7:43

MP3•Episode home

Archived series ("Inactive feed" status)

When? This feed was archived on July 14, 2021 01:41 (3y ago). Last successful fetch was on June 05, 2018 17:42 (6y ago)

Why? Inactive feed status. Our servers were unable to retrieve a valid podcast feed for a sustained period.

What now? You might be able to find a more up-to-date version using the search function. This series will no longer be checked for updates. If you believe this to be in error, please check if the publisher's feed link below is valid and contact support to request the feed be restored or if you have any other concerns about this.

According to The Pragmatic Programmer by Andy Hunt and Dave Thomas, "Every piece of knowledge must have a single, unambiguous, authoritative representation within a system." Last week I talked about extending your Ruby on Rails application. This is because in many cases in order to avoid repeating your logic across multiple classes (models or controllers) you need another place to put your functionality. Mix-in modules, plugins, and single table inheritance all allow you to codify your knowledge into a single place depending on what you’re working with. The DRY principle is more than just a way to avoid having to update multiple files when something changes. Rather, it’s a way of assuring yourself that things are done in a consistent manner. It also helps you when you’re trying to find something in your application because there’s only one place where it can be found.

33 episodes

#Tech #Ruby On Rails #Charles Max Wood