tag:blogger.com,1999:blog-1411318107979111159.post1347667800825715049..comments2023-02-11T05:20:07.941-08:00Comments on Forrester Footnotes: SOLID vs GRASPCurtis Forresterhttp://www.blogger.com/profile/07743918911076130670noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-1411318107979111159.post-38401003392975843532013-03-21T07:25:37.225-07:002013-03-21T07:25:37.225-07:00Yup - with that I agree. The interface and behavio...Yup - with that I agree. The interface and behavior is your contract. One of the guys I'm now working with, though, feels that you should not change or improve the code at all because in a large team someone may have already adapted even to your bugs or wrong behavior and if you fix it you'll then break them. While that is a good point I think it's better to figure out what/who is using the method that you're going to fix and let them know about the change and potential problem. And, if you and they both have unit tests you run the suite. If the tests pass you're golden. Curtis Forresterhttps://www.blogger.com/profile/07743918911076130670noreply@blogger.comtag:blogger.com,1999:blog-1411318107979111159.post-4771754670193669612013-03-21T03:54:12.152-07:002013-03-21T03:54:12.152-07:00You point good. Many theory but reality different....You point good. Many theory but reality different. But I think solid good too. For me "O" is only for interfaces and for behaving. Not change how class works.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-1411318107979111159.post-74274544320579282092013-03-20T06:33:36.457-07:002013-03-20T06:33:36.457-07:00No pictures.No pictures.grantbobhttps://www.blogger.com/profile/08320224292971164407noreply@blogger.com