<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Presentations</title>
	<atom:link href="http://misko.hevery.com/presentations/feed/" rel="self" type="application/rss+xml" />
	<link>http://misko.hevery.com</link>
	<description>Testability Explorer</description>
	<lastBuildDate>Thu, 19 Jan 2012 16:42:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Extreme Enthusiasm &#187; Blog Archive &#187; How I remembered Object Thinking</title>
		<link>http://misko.hevery.com/presentations/comment-page-1/#comment-14148</link>
		<dc:creator>Extreme Enthusiasm &#187; Blog Archive &#187; How I remembered Object Thinking</dc:creator>
		<pubDate>Tue, 13 Dec 2011 21:58:11 +0000</pubDate>
		<guid isPermaLink="false">http://misko.hevery.com/?page_id=555#comment-14148</guid>
		<description>[...] OOP. I learned about the GOF patterns. I learned about the SOLID principles. I learned how to write testable code. I learned how to do TDD for the infrastructure. I learned how to test-drive Chicago style and [...]</description>
		<content:encoded><![CDATA[<p>[...] OOP. I learned about the GOF patterns. I learned about the SOLID principles. I learned how to write testable code. I learned how to do TDD for the infrastructure. I learned how to test-drive Chicago style and [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: misko</title>
		<link>http://misko.hevery.com/presentations/comment-page-1/#comment-8028</link>
		<dc:creator>misko</dc:creator>
		<pubDate>Thu, 05 May 2011 16:21:15 +0000</pubDate>
		<guid isPermaLink="false">http://misko.hevery.com/?page_id=555#comment-8028</guid>
		<description>@Kevin,

the thought has crossed my mind, but it is a lot of work. :-)</description>
		<content:encoded><![CDATA[<p>@Kevin,</p>
<p>the thought has crossed my mind, but it is a lot of work. <img src='http://misko.hevery.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin</title>
		<link>http://misko.hevery.com/presentations/comment-page-1/#comment-7964</link>
		<dc:creator>Kevin</dc:creator>
		<pubDate>Mon, 02 May 2011 07:10:41 +0000</pubDate>
		<guid isPermaLink="false">http://misko.hevery.com/?page_id=555#comment-7964</guid>
		<description>Wow.. these talks are really helpful. It really changes the way I think about coding. I think you should write a book on this subject with more real work examples. I know I would buy this book so are the rest of my teammates.</description>
		<content:encoded><![CDATA[<p>Wow.. these talks are really helpful. It really changes the way I think about coding. I think you should write a book on this subject with more real work examples. I know I would buy this book so are the rest of my teammates.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: misko</title>
		<link>http://misko.hevery.com/presentations/comment-page-1/#comment-6990</link>
		<dc:creator>misko</dc:creator>
		<pubDate>Tue, 01 Mar 2011 18:37:35 +0000</pubDate>
		<guid isPermaLink="false">http://misko.hevery.com/?page_id=555#comment-6990</guid>
		<description>@Aurelien
I have not released the docs under any official license, but you are free to use/translate the slides, as long as you keep a link to the originals for attribution. Other then that, feel free to spread the word, and educate others.

-- Misko</description>
		<content:encoded><![CDATA[<p>@Aurelien<br />
I have not released the docs under any official license, but you are free to use/translate the slides, as long as you keep a link to the originals for attribution. Other then that, feel free to spread the word, and educate others.</p>
<p>&#8211; Misko</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aurélien</title>
		<link>http://misko.hevery.com/presentations/comment-page-1/#comment-6978</link>
		<dc:creator>Aurélien</dc:creator>
		<pubDate>Tue, 01 Mar 2011 07:31:32 +0000</pubDate>
		<guid isPermaLink="false">http://misko.hevery.com/?page_id=555#comment-6978</guid>
		<description>Hi Misko,

I&#039;m thinking of using some of these slides, translating them (in french) and making a similar presentation in my company. What license are they under ? Are you OK with this ?
Thanks for your great website &amp; presentations !</description>
		<content:encoded><![CDATA[<p>Hi Misko,</p>
<p>I&#8217;m thinking of using some of these slides, translating them (in french) and making a similar presentation in my company. What license are they under ? Are you OK with this ?<br />
Thanks for your great website &amp; presentations !</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: misko</title>
		<link>http://misko.hevery.com/presentations/comment-page-1/#comment-5437</link>
		<dc:creator>misko</dc:creator>
		<pubDate>Wed, 22 Dec 2010 11:08:37 +0000</pubDate>
		<guid isPermaLink="false">http://misko.hevery.com/?page_id=555#comment-5437</guid>
		<description>@Alex,

I think your solution is what I would have suggested as well. You need to put a layer of indirection between you and them. My only suggestion would be to not make the api match exactly what they give you but rather create an ideal API for yourself. That way your your code using these dependencies is simpler. Also if the external APIs change than the only things you have to change is the adapter and not all of the instances. You may have a hard time testing the adapters, but the rest of the system should be fine.

-- misko</description>
		<content:encoded><![CDATA[<p>@Alex,</p>
<p>I think your solution is what I would have suggested as well. You need to put a layer of indirection between you and them. My only suggestion would be to not make the api match exactly what they give you but rather create an ideal API for yourself. That way your your code using these dependencies is simpler. Also if the external APIs change than the only things you have to change is the adapter and not all of the instances. You may have a hard time testing the adapters, but the rest of the system should be fine.</p>
<p>&#8211; misko</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://misko.hevery.com/presentations/comment-page-1/#comment-5432</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Wed, 22 Dec 2010 03:33:26 +0000</pubDate>
		<guid isPermaLink="false">http://misko.hevery.com/?page_id=555#comment-5432</guid>
		<description>Thanks for great presentations.
Talk, related to functional approach and avoiding &#039;if&#039; statements really helped to order my clustered knowledge bas into a single, focused one.
One question about working with legacy applications: I have really evil Singleton of Singletons: it&#039;s ResourceLocator, which is used application-wide to pull other Singletons (each one is totally untestable and out of my control: no interfaces, just plain classes, JNDI resources pulling in constructors, lots of static methods etc.) - I can&#039;t mock them and/or substitute (because of JNDI in constructors). There&#039;s no need to say, that dependent code is totally untestable. We can&#039;t get rid of these proxies (it&#039;s external systems proxies and we don&#039;t own the codebase), but I really want to isolate all the new code from them. The only acceptable solution I found is to create separate interfaces, which will have same method signatures and use dynamic adapters, which will redirect all calls addressed from generated dynamic proxies to old Singletons. The only drawback: in case of any API changes we have to re-generate these interfaces to reflect the changes (it&#039;s like relationship between Bean and Remote/Local interfaces in EJB). Any other possible solutions, how to isolate these proxies?</description>
		<content:encoded><![CDATA[<p>Thanks for great presentations.<br />
Talk, related to functional approach and avoiding &#8216;if&#8217; statements really helped to order my clustered knowledge bas into a single, focused one.<br />
One question about working with legacy applications: I have really evil Singleton of Singletons: it&#8217;s ResourceLocator, which is used application-wide to pull other Singletons (each one is totally untestable and out of my control: no interfaces, just plain classes, JNDI resources pulling in constructors, lots of static methods etc.) &#8211; I can&#8217;t mock them and/or substitute (because of JNDI in constructors). There&#8217;s no need to say, that dependent code is totally untestable. We can&#8217;t get rid of these proxies (it&#8217;s external systems proxies and we don&#8217;t own the codebase), but I really want to isolate all the new code from them. The only acceptable solution I found is to create separate interfaces, which will have same method signatures and use dynamic adapters, which will redirect all calls addressed from generated dynamic proxies to old Singletons. The only drawback: in case of any API changes we have to re-generate these interfaces to reflect the changes (it&#8217;s like relationship between Bean and Remote/Local interfaces in EJB). Any other possible solutions, how to isolate these proxies?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: &#187; Example project workflow using SWCs</title>
		<link>http://misko.hevery.com/presentations/comment-page-1/#comment-3662</link>
		<dc:creator>&#187; Example project workflow using SWCs</dc:creator>
		<pubDate>Mon, 28 Jun 2010 01:09:23 +0000</pubDate>
		<guid isPermaLink="false">http://misko.hevery.com/?page_id=555#comment-3662</guid>
		<description>[...] checkout those fantastic Miško Hevery presentations. Miško talks about why tests is so important, why beware of Singletons, how to use dependency [...]</description>
		<content:encoded><![CDATA[<p>[...] checkout those fantastic Miško Hevery presentations. Miško talks about why tests is so important, why beware of Singletons, how to use dependency [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: &#187; Example project workflow using SWCs</title>
		<link>http://misko.hevery.com/presentations/comment-page-1/#comment-3659</link>
		<dc:creator>&#187; Example project workflow using SWCs</dc:creator>
		<pubDate>Sat, 26 Jun 2010 15:01:41 +0000</pubDate>
		<guid isPermaLink="false">http://misko.hevery.com/?page_id=555#comment-3659</guid>
		<description>[...] checkout those fantastic Mi?ko Hevery presentations. Mi?ko talks about why tests is so important, why beware of Singletons, how to use dependency [...]</description>
		<content:encoded><![CDATA[<p>[...] checkout those fantastic Mi?ko Hevery presentations. Mi?ko talks about why tests is so important, why beware of Singletons, how to use dependency [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ayumilove</title>
		<link>http://misko.hevery.com/presentations/comment-page-1/#comment-3457</link>
		<dc:creator>ayumilove</dc:creator>
		<pubDate>Fri, 07 May 2010 14:51:46 +0000</pubDate>
		<guid isPermaLink="false">http://misko.hevery.com/?page_id=555#comment-3457</guid>
		<description>could you make another presentation on Testing Services with Value Objects :O</description>
		<content:encoded><![CDATA[<p>could you make another presentation on Testing Services with Value Objects :O</p>
]]></content:encoded>
	</item>
</channel>
</rss>

