Comments on: Seams: Some thoughts http://www.markhneedham.com/blog/2009/06/21/seams-some-thoughts/ Thoughts on Software Development Fri, 19 Mar 2010 07:53:28 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Book Club: Working Effectively With Legacy Code – Chapters 3,4 & 5 (Michael Feathers) at Mark Needham http://www.markhneedham.com/blog/2009/06/21/seams-some-thoughts/comment-page-1/#comment-24923 Book Club: Working Effectively With Legacy Code – Chapters 3,4 & 5 (Michael Feathers) at Mark Needham Mon, 19 Oct 2009 21:02:44 +0000 http://www.markhneedham.com/blog/?p=1361#comment-24923 [...] really like the idea of seams and enabling points to describe how we can alter the way that our code works by making changes in [...] [...] really like the idea of seams and enabling points to describe how we can alter the way that our code works by making changes in [...]

]]> By: Impersonators: Finding the enabling point at Mark Needham http://www.markhneedham.com/blog/2009/06/21/seams-some-thoughts/comment-page-1/#comment-21518 Impersonators: Finding the enabling point at Mark Needham Tue, 18 Aug 2009 14:45:25 +0000 http://www.markhneedham.com/blog/?p=1361#comment-21518 [...] like to use the term 'enabling point', which I learnt from Michael Feathers in his chapter on seams in Working Effectively With Legacy Code, to describe the place where we can make the decision to [...] [...] like to use the term 'enabling point', which I learnt from Michael Feathers in his chapter on seams in Working Effectively With Legacy Code, to describe the place where we can make the decision to [...]

]]> By: Impersonators: Why do we need them? at Mark Needham http://www.markhneedham.com/blog/2009/06/21/seams-some-thoughts/comment-page-1/#comment-21444 Impersonators: Why do we need them? at Mark Needham Sun, 16 Aug 2009 12:13:49 +0000 http://www.markhneedham.com/blog/?p=1361#comment-21444 [...] wrote previously about an impersonator we are using on my project which Martin Fowler has dubbed the 'self initializing fake' and although I thought this was the [...] [...] wrote previously about an impersonator we are using on my project which Martin Fowler has dubbed the 'self initializing fake' and although I thought this was the [...]

]]> By: Continuous Integration: Community College Discussion at Mark Needham http://www.markhneedham.com/blog/2009/06/21/seams-some-thoughts/comment-page-1/#comment-19952 Continuous Integration: Community College Discussion at Mark Needham Sat, 11 Jul 2009 04:15:09 +0000 http://www.markhneedham.com/blog/?p=1361#comment-19952 [...] my project we are also making use of an impersonator of our main integration point early in our build pipeline and then testing end to end integration [...] [...] my project we are also making use of an impersonator of our main integration point early in our build pipeline and then testing end to end integration [...]

]]> By: Reflective Perspective - Chris Alcock » The Morning Brew #374 http://www.markhneedham.com/blog/2009/06/21/seams-some-thoughts/comment-page-1/#comment-19059 Reflective Perspective - Chris Alcock » The Morning Brew #374 Tue, 23 Jun 2009 06:53:22 +0000 http://www.markhneedham.com/blog/?p=1361#comment-19059 [...] Seams: Some thoughts - Mark Needham talks about the idea of ’seams’, places where you can change the behaviour of a program without editing the code in that place, looking at some possible candidate seams in systems generally. [...] [...] Seams: Some thoughts – Mark Needham talks about the idea of 'seams', places where you can change the behaviour of a program without editing the code in that place, looking at some possible candidate seams in systems generally. [...]

]]> By: Jen Smith http://www.markhneedham.com/blog/2009/06/21/seams-some-thoughts/comment-page-1/#comment-18976 Jen Smith Sun, 21 Jun 2009 11:14:19 +0000 http://www.markhneedham.com/blog/?p=1361#comment-18976 (Michael Feather's book is great - especially as it is structured as a series of 'what ifs' so you can dip into the part you need. More books need to be written this way!) I think the onus for creating testable code, suitable seams and removing external dependencies should be on the 3rd party provider itself. APIs should come with test utilies, stubs etc. where possible. OK so we are a long way off from that, but it's definitely the right direction! (Michael Feather's book is great – especially as it is structured as a series of 'what ifs' so you can dip into the part you need. More books need to be written this way!)

I think the onus for creating testable code, suitable seams and removing external dependencies should be on the 3rd party provider itself. APIs should come with test utilies, stubs etc. where possible. OK so we are a long way off from that, but it's definitely the right direction!

]]>