Comments for Fragmental.tw http://fragmental.tw Repeat after me: Data is code, code is data. Sun, 21 Mar 2010 07:06:07 +0000 http://wordpress.org/?v=2.5 Comment on Everyday Tales: Anatomy of a Refactoring – Part 3 by Luis Sergio Oliveira http://fragmental.tw/2010/03/10/everyday-tales-anatomy-of-a-refactoring-%e2%80%93-part-3/#comment-2199 Luis Sergio Oliveira Sat, 13 Mar 2010 18:50:33 +0000 http://fragmental.tw/?p=162#comment-2199 I think that you'll get into a situation where UserRepository will be a mess and it will be responsible for the majority of the bugs. I have a proposal: since the application is a kind of aggregation of several other applications, I suggest that the fact that the application User should also be related to several other users. So, you have a UberUser and normal User for each of the aggregated other applications. Nevertheless, UserRepository should be split in several classes, each implementing only one responsibility. Besides diagrams, could you show us some code? I think that you’ll get into a situation where UserRepository will be a mess and it will be responsible for the majority of the bugs.

I have a proposal: since the application is a kind of aggregation of several other applications, I suggest that the fact that the application User should also be related to several other users. So, you have a UberUser and normal User for each of the aggregated other applications.

Nevertheless, UserRepository should be split in several classes, each implementing only one responsibility.

Besides diagrams, could you show us some code?

]]> Comment on Everyday Tales: Anatomy of a Refactoring – Part 3 by sud http://fragmental.tw/2010/03/10/everyday-tales-anatomy-of-a-refactoring-%e2%80%93-part-3/#comment-2197 sud Thu, 11 Mar 2010 23:43:22 +0000 http://fragmental.tw/?p=162#comment-2197 Thanks for posting this series. It really helps when you can see how code evolves naturally/logically to become more well designed. Thanks for posting this series. It really helps when you can see how code evolves naturally/logically to become more well designed.

]]> Comment on Everyday Tales: Anatomy of a Refactoring by Everyday Tales: Anatomy of a Refactoring – Part 2 at Fragmental.tw http://fragmental.tw/2010/02/24/everyday-tales-anatomy-of-a-refactoring/#comment-2194 Everyday Tales: Anatomy of a Refactoring – Part 2 at Fragmental.tw Wed, 10 Mar 2010 12:44:41 +0000 http://fragmental.tw/?p=160#comment-2194 [...] Research « Everyday Tales: Anatomy of a Refactoring [...] […] Research « Everyday Tales: Anatomy of a Refactoring […]

]]> Comment on Everyday Tales: Anatomy of a Refactoring by Leandro Herrera http://fragmental.tw/2010/02/24/everyday-tales-anatomy-of-a-refactoring/#comment-2193 Leandro Herrera Tue, 09 Mar 2010 13:07:15 +0000 http://fragmental.tw/?p=160#comment-2193 Hey Phillip! How did you solve the problem? I'm curious about it... :P Hey Phillip! How did you solve the problem? I’m curious about it… :P

]]> Comment on Duke Nukem Forever and Magic Bags of Money by O processo de deploy contínuo | blog.caelum.com.br http://fragmental.tw/2009/12/22/duke-nukem-forever-and-magic-bags-of-money/#comment-2191 O processo de deploy contínuo | blog.caelum.com.br Wed, 03 Mar 2010 21:16:10 +0000 http://fragmental.tw/?p=158#comment-2191 [...] Ao término do primeiro sprint, sua aplicação está andando muito bem e tem todas as histórias aprovadas enquanto no ambiente de testes. Passaremos então para a primeira tentativa de colocá-lo em produção/homologação, e logo descobre-se que o sistema não funciona corretamente nesse novo ambiente, e é gasto muita energia para adaptar diversos detalhes que já eram considerados “prontos”. [...] […] Ao término do primeiro sprint, sua aplicação está andando muito bem e tem todas as histórias aprovadas enquanto no ambiente de testes. Passaremos então para a primeira tentativa de colocá-lo em produção/homologação, e logo descobre-se que o sistema não funciona corretamente nesse novo ambiente, e é gasto muita energia para adaptar diversos detalhes que já eram considerados “prontos”. […]

]]> Comment on Everyday Tales: Anatomy of a Refactoring by Camilo Telles http://fragmental.tw/2010/02/24/everyday-tales-anatomy-of-a-refactoring/#comment-2189 Camilo Telles Sat, 27 Feb 2010 11:18:45 +0000 http://fragmental.tw/?p=160#comment-2189 Dear Mr. Calçado, What is your contact? I want to hire you (ThoughtWorks) for a job in Brasil. Regards Camilo Telles Dear Mr. Calçado,

What is your contact? I want to hire you (ThoughtWorks) for a job in Brasil.

Regards

Camilo Telles

]]> Comment on Everyday Tales: Anatomy of a Refactoring by Leandro http://fragmental.tw/2010/02/24/everyday-tales-anatomy-of-a-refactoring/#comment-2184 Leandro Thu, 25 Feb 2010 13:31:21 +0000 http://fragmental.tw/?p=160#comment-2184 I enjoy this 'Everyday Tales' new journey! "writing about some smaller/simpler problems and solutions would be better than not blogging at all." :) yeah... I must confess that I had should read it twice to understand the solution. My brain is very slow. The "models" (#UML) helped a lot. Keep telling us more the 'Everyday Tales'! I enjoy this ‘Everyday Tales’ new journey!
“writing about some smaller/simpler problems and solutions would be better than not blogging at all.” :) yeah… I must confess that I had should read it twice to understand the solution. My brain is very slow. The “models” (#UML) helped a lot. Keep telling us more the ‘Everyday Tales’!

]]> Comment on Everyday Tales: Anatomy of a Refactoring by Luis Sergio Oliveira http://fragmental.tw/2010/02/24/everyday-tales-anatomy-of-a-refactoring/#comment-2183 Luis Sergio Oliveira Thu, 25 Feb 2010 05:31:58 +0000 http://fragmental.tw/?p=160#comment-2183 To elaborate a bit more on my comment, I think that UserRepository continued to be a class with more than one responsibility, although you had the nice interfaces for it. So, it is like having one object that is actually two objects and has two set of needs to satisfy two related, but, different responsibilities... But, I don't want to spoil the story, please give your readers the 2nd part in the same step by step and clear style :-) To elaborate a bit more on my comment, I think that UserRepository continued to be a class with more than one responsibility, although you had the nice interfaces for it. So, it is like having one object that is actually two objects and has two set of needs to satisfy two related, but, different responsibilities…

But, I don’t want to spoil the story, please give your readers the 2nd part in the same step by step and clear style :-)

]]> Comment on Everyday Tales: Anatomy of a Refactoring by Luis Sergio Oliveira http://fragmental.tw/2010/02/24/everyday-tales-anatomy-of-a-refactoring/#comment-2182 Luis Sergio Oliveira Thu, 25 Feb 2010 05:16:00 +0000 http://fragmental.tw/?p=160#comment-2182 Hi Phillip, very nice and clear write-up of the circular dependency problems, which normally occur in almost all real world projects I've seen so far. The solution will be to take the plunge and break-up UserRepository in pieces, right? Hi Phillip,

very nice and clear write-up of the circular dependency problems, which normally occur in almost all real world projects I’ve seen so far.

The solution will be to take the plunge and break-up UserRepository in pieces, right?

]]> Comment on Everyday Tales: Anatomy of a Refactoring by Rodrigo Yoshima http://fragmental.tw/2010/02/24/everyday-tales-anatomy-of-a-refactoring/#comment-2181 Rodrigo Yoshima Thu, 25 Feb 2010 04:07:33 +0000 http://fragmental.tw/?p=160#comment-2181 Nice to help you guys from TW. (BTW #UML #FTW ;)) Nice to help you guys from TW.

(BTW #UML #FTW ;))

]]>