Comments on: Loose coupling is overrated. http://www.makinggoodsoftware.com/2009/12/30/lose-coupling-is-overrated/ Thu, 29 Jul 2010 10:36:55 -0600 http://wordpress.org/?v=2.8.3 hourly 1 By: Tweets that mention Lose coupling is overrated. | Making Good Software -- Topsy.com http://www.makinggoodsoftware.com/2009/12/30/lose-coupling-is-overrated/comment-page-1/#comment-3330 Tweets that mention Lose coupling is overrated. | Making Good Software -- Topsy.com Wed, 30 Dec 2009 19:33:21 +0000 http://www.makinggoodsoftware.com/?p=1181#comment-3330 [...] This post was mentioned on Twitter by Hélio Costa, OlivierBeauvais. OlivierBeauvais said: Lose coupling is overrated. #agile http://bit.ly/4Gl7w0 [...] [...] This post was mentioned on Twitter by Hélio Costa, OlivierBeauvais. OlivierBeauvais said: Lose coupling is overrated. #agile http://bit.ly/4Gl7w0 [...]

]]> By: Macaca http://www.makinggoodsoftware.com/2009/12/30/lose-coupling-is-overrated/comment-page-1/#comment-3328 Macaca Wed, 30 Dec 2009 19:11:37 +0000 http://www.makinggoodsoftware.com/?p=1181#comment-3328 We have the policy to look at each others work (especially if it goes in the library), look at what is being done and simply state: 'make it simpler'. One thing that's a guidelien (not a rule) is to look at code without actually reading it: how many imports? How many members? How many of each access-type? How much lines for each methods? We have the policy to look at each others work (especially if it goes in the library), look at what is being done and simply state: ‘make it simpler’.

One thing that’s a guidelien (not a rule) is to look at code without actually reading it: how many imports? How many members? How many of each access-type? How much lines for each methods?

]]>