# Redundancy in controller? What are your thoughts?

**URL:** <https://www.ruby-forum.com/t/redundancy-in-controller-what-are-your-thoughts/90120>\
**Category:** Rails\
**Created:** [March 26, 2007, 7:28am UTC](https://www.ruby-forum.com/t/redundancy-in-controller-what-are-your-thoughts/90120 "2007-03-26T07:28:22Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![benjohnson](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/3ec8ea/32.png) [@benjohnson](https://www.ruby-forum.com/u/benjohnson)\
**Post date:** [March 26, 2007, 7:28am UTC](https://www.ruby-forum.com/t/redundancy-in-controller-what-are-your-thoughts/90120/1 "2007-03-26T07:28:22Z")

</div>

I am having a tough time coming up with a decision on this:

Is it ok to have redundancy in your controllers and views for the sake  
of flexibility? Or should your controllers and views be 100% DRY by  
creating private methods in your controllers that accept parameters and  
using partials that accepts locals?

I tried being 100% DRY but my private methods are getting very complex  
and my partials are getting complex as well, with a bunch of if  
statements, etc.

I feel like redundancy in your models is bad, but in your controller and  
views it’s not so bad because this is the presentation end of your  
application which can vary depending on the section of your application.

What do you think?