Comments on: Day 7: Give Only One Responsibility to Each Class http://coliveira.net/software/day-7-give-only-one-responsibility-for-each-class/ by Carlos Oliveira Wed, 25 Jan 2012 12:13:28 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Weekly Link Post 101 « Rhonda Tipton’s WebLog http://coliveira.net/software/day-7-give-only-one-responsibility-for-each-class/comment-page-1/#comment-299 Weekly Link Post 101 « Rhonda Tipton’s WebLog Sun, 12 Jul 2009 22:18:12 +0000 http://coliveira.net/2009/07/day-7-give-only-one-responsibility-for-each-class/#comment-299 [...] Carlos Oliveira continues a series on How to become a better developer in 30 days. Day 7: Give Only One Responsibility to Each Class. [...] [...] Carlos Oliveira continues a series on How to become a better developer in 30 days. Day 7: Give Only One Responsibility to Each Class. [...]

]]> By: Veera http://coliveira.net/software/day-7-give-only-one-responsibility-for-each-class/comment-page-1/#comment-261 Veera Sat, 04 Jul 2009 07:22:18 +0000 http://coliveira.net/2009/07/day-7-give-only-one-responsibility-for-each-class/#comment-261 Most of the programmer who came from the procedural language background, usually do this mistake: the stuff all their business into a single method/class. But, in the long run, this mistake will turn into nightmare for the maintainer. Most of the programmer who came from the procedural language background, usually do this mistake: the stuff all their business into a single method/class.

But, in the long run, this mistake will turn into nightmare for the maintainer.

]]> By: kureikain http://coliveira.net/software/day-7-give-only-one-responsibility-for-each-class/comment-page-1/#comment-260 kureikain Sat, 04 Jul 2009 05:46:57 +0000 http://coliveira.net/2009/07/day-7-give-only-one-responsibility-for-each-class/#comment-260 Hmm... we sometimes must break this rule! Because we can make fragment w/ this since we're dividing reponsibility to many class! Hmm… we sometimes must break this rule!
Because we can make fragment w/ this since we’re dividing reponsibility to many class!

]]>