<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The Sympriser Blog</title>
	<atom:link href="http://blog.symprise.net/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.symprise.net</link>
	<description>Synergising the Enterprise through Software &#38; Management Innovation</description>
	<lastBuildDate>Sat, 29 Dec 2018 00:59:08 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=4.5.20</generator>
	<item>
		<title>The Surprising Truth About What Motivates Us</title>
		<link>http://blog.symprise.net/2010/05/15/the-surprising-truth-about-what-motivates-us/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=the-surprising-truth-about-what-motivates-us</link>
		<comments>http://blog.symprise.net/2010/05/15/the-surprising-truth-about-what-motivates-us/#respond</comments>
		<pubDate>Sat, 15 May 2010 22:26:29 +0000</pubDate>
		<dc:creator><![CDATA[Rafael Peixoto Azevedo]]></dc:creator>
				<category><![CDATA[Leadership]]></category>

		<guid isPermaLink="false">http://blog.symprise.net/?p=2143</guid>
		<description><![CDATA[Great illustration by Cognitive Media of Daniel Pink's presentation at the Royal Society for the encouragement of Arts, Manufactures and Commerce (RSA) based on his book  "Drive: The Surprising Truth About What Motivates Us".]]></description>
		<wfw:commentRss>http://blog.symprise.net/2010/05/15/the-surprising-truth-about-what-motivates-us/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Open/Closed Principle: Concerns about Change in Software Design</title>
		<link>http://blog.symprise.net/2009/06/23/open-closed-principle-concerns-about-change-in-software-design/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=open-closed-principle-concerns-about-change-in-software-design</link>
		<comments>http://blog.symprise.net/2009/06/23/open-closed-principle-concerns-about-change-in-software-design/#comments</comments>
		<pubDate>Tue, 23 Jun 2009 06:11:58 +0000</pubDate>
		<dc:creator><![CDATA[Rafael Peixoto de Azevedo]]></dc:creator>
				<category><![CDATA[General Principles]]></category>
		<category><![CDATA[Object Oriented]]></category>
		<category><![CDATA[Software Design]]></category>

		<guid isPermaLink="false">http://sympriser.wordpress.com/?p=1727</guid>
		<description><![CDATA[High quality software designs are easier and safer to work with. Investing in quality demands discipline and skill. Good design principles are usually helpful. But, are they always applicable?

This post investigates the applicability of the “Open-Closed Principle” when we add new functionality to a software design whose source code is entirely under our control.

Our argument is based on Dijkstra’s concept of separation of concerns.]]></description>
		<wfw:commentRss>http://blog.symprise.net/2009/06/23/open-closed-principle-concerns-about-change-in-software-design/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Revisiting Fowler&#8217;s Video Store: Refactoring Code, Refining Abstractions</title>
		<link>http://blog.symprise.net/2009/04/28/revisiting-fowlers-video-store-refactoring-code-reengineering-abstractions/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=revisiting-fowlers-video-store-refactoring-code-reengineering-abstractions</link>
		<comments>http://blog.symprise.net/2009/04/28/revisiting-fowlers-video-store-refactoring-code-reengineering-abstractions/#comments</comments>
		<pubDate>Tue, 28 Apr 2009 12:42:42 +0000</pubDate>
		<dc:creator><![CDATA[Rafael Peixoto de Azevedo]]></dc:creator>
				<category><![CDATA[Domain-Driven]]></category>
		<category><![CDATA[Featured]]></category>
		<category><![CDATA[Object Oriented]]></category>
		<category><![CDATA[Refactoring]]></category>
		<category><![CDATA[Software Development]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[Revisiting Fowler's Video Store]]></category>

		<guid isPermaLink="false">http://sympriser.wordpress.com/?p=744</guid>
		<description><![CDATA[Refactoring techniques and Design Patterns have been extensively propagated and advocated for over a decade now. <strong>Why we still find hard to change, anaemic or overly complex object oriented structures?</strong> What is missing in our design practices?

In this series, we use Fowler's didactic Video Store program to show <strong>practical advanced refactoring strategies</strong> that effectively improve design simplicity, expressiveness and flexibility.]]></description>
		<wfw:commentRss>http://blog.symprise.net/2009/04/28/revisiting-fowlers-video-store-refactoring-code-reengineering-abstractions/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Revisiting Fowler&#8217;s Video Store: Variants and Invariants</title>
		<link>http://blog.symprise.net/2009/04/24/revisiting-fowlers-video-store-03-variants-and-invariants/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=revisiting-fowlers-video-store-03-variants-and-invariants</link>
		<comments>http://blog.symprise.net/2009/04/24/revisiting-fowlers-video-store-03-variants-and-invariants/#comments</comments>
		<pubDate>Fri, 24 Apr 2009 16:21:46 +0000</pubDate>
		<dc:creator><![CDATA[Rafael Peixoto de Azevedo]]></dc:creator>
				<category><![CDATA[Domain-Driven]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[Object Oriented]]></category>
		<category><![CDATA[Refactoring]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[Revisiting Fowler's Video Store]]></category>

		<guid isPermaLink="false">http://sympriser.wordpress.com/?p=1252</guid>
		<description><![CDATA[This post resumes the Revisiting Fowler's Video Store series. After making the relevant domain concepts explicit, we focus our refactoring process on another aspect of domain semantics, studying <strong>contextual variance</strong> under the perspective of the following issues:
   1. The Passage of Time;
   2. Changes in the Video Classification;
   3. Changes in Rental Prices and Terms.]]></description>
		<wfw:commentRss>http://blog.symprise.net/2009/04/24/revisiting-fowlers-video-store-03-variants-and-invariants/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Revisiting Fowler&#8217;s Video Store: Making Implicit Concepts Explicit</title>
		<link>http://blog.symprise.net/2009/03/31/revisiting-fowlers-video-store-02-making-implicit-concepts-explicit/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=revisiting-fowlers-video-store-02-making-implicit-concepts-explicit</link>
		<comments>http://blog.symprise.net/2009/03/31/revisiting-fowlers-video-store-02-making-implicit-concepts-explicit/#comments</comments>
		<pubDate>Tue, 31 Mar 2009 13:39:29 +0000</pubDate>
		<dc:creator><![CDATA[Rafael Peixoto de Azevedo]]></dc:creator>
				<category><![CDATA[Domain-Driven]]></category>
		<category><![CDATA[Extract Value Object]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[Object Oriented]]></category>
		<category><![CDATA[Refactoring]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[Revisiting Fowler's Video Store]]></category>

		<guid isPermaLink="false">http://sympriser.wordpress.com/?p=716</guid>
		<description><![CDATA[Domain-Driven Design situates the domain model in a central and convergent role, tightly articulating semantics and syntax for problem definition, solution design and software implementation.
<p>
<strong>In this post, we bring the domain semantics to our refactoring process.</strong> We want a deeper perspective to analyse modularity problems and to direct improvements towards greater relevance to our design objectives.]]></description>
		<wfw:commentRss>http://blog.symprise.net/2009/03/31/revisiting-fowlers-video-store-02-making-implicit-concepts-explicit/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Revisiting Fowler&#8217;s Video Store: Adopting Object Oriented Syntax</title>
		<link>http://blog.symprise.net/2009/01/14/revisiting-fowlers-video-store-01-object-oriented-syntax/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=revisiting-fowlers-video-store-01-object-oriented-syntax</link>
		<comments>http://blog.symprise.net/2009/01/14/revisiting-fowlers-video-store-01-object-oriented-syntax/#respond</comments>
		<pubDate>Wed, 14 Jan 2009 05:36:02 +0000</pubDate>
		<dc:creator><![CDATA[Rafael Peixoto de Azevedo]]></dc:creator>
				<category><![CDATA[Java]]></category>
		<category><![CDATA[Object Oriented]]></category>
		<category><![CDATA[Refactoring]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[Revisiting Fowler's Video Store]]></category>

		<guid isPermaLink="false">http://sympriser.wordpress.com/?p=603</guid>
		<description><![CDATA[Have you ever found a program you needed to add, change or even fix a simple function, but you just didn’t know where to start or were afraid of breaking the program’s logical consistency?

<strong>Refactoring</strong> is a modularity improving technique that is indispensable in the skill set of any professional software developer. In this post, we use Refactoring to effectively adopt an object-oriented design syntax and make a program like this easier and safer to work with.]]></description>
		<wfw:commentRss>http://blog.symprise.net/2009/01/14/revisiting-fowlers-video-store-01-object-oriented-syntax/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PM Effectiveness &#8211; The Experience Trap</title>
		<link>http://blog.symprise.net/2008/05/05/pm-effectiveness-the-experience-trap/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=pm-effectiveness-the-experience-trap</link>
		<comments>http://blog.symprise.net/2008/05/05/pm-effectiveness-the-experience-trap/#respond</comments>
		<pubDate>Mon, 05 May 2008 17:23:54 +0000</pubDate>
		<dc:creator><![CDATA[Rafael Peixoto de Azevedo]]></dc:creator>
				<category><![CDATA[Featured]]></category>
		<category><![CDATA[Leadership]]></category>
		<category><![CDATA[Management]]></category>
		<category><![CDATA[Project]]></category>
		<category><![CDATA[PM Effectiveness]]></category>
		<category><![CDATA[The Experience Trap]]></category>

		<guid isPermaLink="false">http://sympriser.wordpress.com/?p=403</guid>
		<description><![CDATA["Experienced project managers can deal more effectively with complex software projects". <strong>Really?</strong>
<p>
This "conventional truth" is contradicted by INSEAD professors Sengupta and Van Wassenhove's research on experience-based learning.]]></description>
		<wfw:commentRss>http://blog.symprise.net/2008/05/05/pm-effectiveness-the-experience-trap/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Trust Requirement</title>
		<link>http://blog.symprise.net/2008/04/15/the-trust-requirement/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=the-trust-requirement</link>
		<comments>http://blog.symprise.net/2008/04/15/the-trust-requirement/#comments</comments>
		<pubDate>Tue, 15 Apr 2008 12:53:40 +0000</pubDate>
		<dc:creator><![CDATA[Rafael Peixoto de Azevedo]]></dc:creator>
				<category><![CDATA[Leadership]]></category>
		<category><![CDATA[Requirements]]></category>

		<guid isPermaLink="false">http://sympriser.wordpress.com/?p=394</guid>
		<description><![CDATA[The perceived credibility of an IT professional goes beyond his or her personal competence and integrity; it is grounded in trustful relationships. This post is a reflection on our professional relationship style. Is it effective to create and nurture trustful relationships?]]></description>
		<wfw:commentRss>http://blog.symprise.net/2008/04/15/the-trust-requirement/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Most Requirements are just Design Decisions</title>
		<link>http://blog.symprise.net/2008/04/15/most-requirements-are-just-design-decisions/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=most-requirements-are-just-design-decisions</link>
		<comments>http://blog.symprise.net/2008/04/15/most-requirements-are-just-design-decisions/#respond</comments>
		<pubDate>Tue, 15 Apr 2008 12:30:24 +0000</pubDate>
		<dc:creator><![CDATA[Rafael Peixoto de Azevedo]]></dc:creator>
				<category><![CDATA[Featured]]></category>
		<category><![CDATA[Requirements]]></category>

		<guid isPermaLink="false">http://sympriser.wordpress.com/?p=392</guid>
		<description><![CDATA[<strong><em>The language we use both reflects and influences our thinking.</em></strong>

The term <strong>“requirements”</strong> has its roots on cartesian and bureaucratic thinking, that supposes a static and impersonal business world where specialists would be able to uncover, extract and document the definitive specifications for software systems.]]></description>
		<wfw:commentRss>http://blog.symprise.net/2008/04/15/most-requirements-are-just-design-decisions/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
