Polymathic

Digital transformation, higher education, innovation, technology, professional skills, management, and strategy


Nested resources in Ruby on Rails: why bother?

Nested resources in Ruby on Rails are sort of neat, but they are a pain to implement. What’s more, I have to ask myself, why bother?

If a resource has a unique identifier id, then why would you need to call its parent resource to call it? The unique identifier is enough. And what resource doesn’t have a unique id these days?


Discover more from Polymathic

Subscribe to get the latest posts sent to your email.



One response to “Nested resources in Ruby on Rails: why bother?”

  1. Anko Painting Avatar
    Anko Painting

    umm, you might want one form (say user details) which multiple addresses, and want that all the be handled by the same form. ie have an add address link and a remove address link.

    or allow adding teams to a user inline. I’ve used nested resources heaps.

Leave a Reply

Your email address will not be published. Required fields are marked *

About Me

Visionary leader driving digital transformation across higher education and Fortune 500 companies. Pioneered AI integration at Emory University, including GenAI and AI agents, while spearheading faculty information systems and student entrepreneurship initiatives. Led crisis management during pandemic, transitioning 200+ courses online and revitalizing continuing education through AI-driven improvements. Designed, built, and launched the Emory Center for Innovation. Combines Ph.D. in Philosophy with deep tech expertise to navigate ethical implications of emerging technologies. International experience includes DAAD fellowship in Germany. Proven track record in thought leadership, workforce development, and driving profitability in diverse sectors.

Favorite sites

  • Daring Fireball

Favorite podcasts

  • Manager Tools

Newsletter

Newsletter