<?xml version="1.0" encoding="UTF-8"?><!-- generator="WordPress/2.5" -->
<rss version="0.92">
<channel>
	<title>Fragmental.tw</title>
	<link>http://fragmental.tw</link>
	<description>Repeat after me: Data is code, code is data.</description>
	<lastBuildDate>Mon, 06 Sep 2010 11:07:54 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	
	<item>
		<title>Thoughts on Abstractions: Part 2 – Abstractions in Your Domain</title>
		<description>As we saw in Part I, abstractions are everywhere. Unfortunately, even though everyone is more than happy to reuse abstractions provided by someone else I often see people failing to identify those in their own code.

Most people tend to create abstractions found using Russ Abbott’s method of using the textual ...</description>
		<link>http://fragmental.tw/2010/09/06/thoughts-on-abstractions-part-2-abstractions-in-your-domain/</link>
			</item>
	<item>
		<title>ThoughtWorks Sydney Open Geek Night this Wednesday!</title>
		<description>Giles says:

A Talk on Seph
ThoughtWorks‘ resident language inventor Ola Bini will be visiting Sydney in September. Ola is one of the four committers on the JRuby project (now the fastest Ruby runtime) and the inventor of the highly experimental prototype-based language Ioke. And we’ve convinced him to give a talk ...</description>
		<link>http://fragmental.tw/2010/09/06/thoughtworks-sydney-open-geek-night-this-wednesday/</link>
			</item>
	<item>
		<title>Thoughts on Abstractions: Part 1 – Abstractions Everywhere</title>
		<description>Update: Part II is here.

Most complex tasks are solved using abstractions. To create an abstraction one groups lower-level concepts, what I will call primitives in this text, and make them interact in a pre-defined way.



Abstractions are present at all levels in a system. Computers work based on electric signals. To ...</description>
		<link>http://fragmental.tw/2010/08/17/thoughts-on-abstractions-part-1-%e2%80%93-abstractions-everywhere/</link>
			</item>
	<item>
		<title>Everyday Tales: We Call it Unit for a Reason</title>
		<description>Last week, Cauê and I were refactoring some classes in our systems and faced an interesting situation.

In our application we have a notifications system. It is quite simple; notifications are read from a text file and shown in a small information box in the home page. The MVC controller –it’s ...</description>
		<link>http://fragmental.tw/2010/06/07/everyday-tales-we-call-it-unit-for-a-reason/</link>
			</item>
	<item>
		<title>Agile Architecture: 4 Common Strategies</title>
		<description>At ThoughtWorks, our preferred way to start a project is by doing a set of workshops and sessions with stakeholders for about two weeks. That’s what we call Inception. After the Inception we usually have a product backlog for the project and are ready to start writing production code.

During that ...</description>
		<link>http://fragmental.tw/2010/05/12/agile-architecture-4-common-strategies/</link>
			</item>
	<item>
		<title>Agile Anti-Patterns: Democratic Design</title>
		<description>Weeks ago, some people in the Ubuntu community got a bit disappointed with the distribution’s core team:


> We are supposed to be a community, we all use Ubuntu and contribute 
> to it, and we deserve some respect regarding these kind of decisions. 
> We all make Ubuntu together, or ...</description>
		<link>http://fragmental.tw/2010/05/09/agile-anti-patterns-democratic-design/</link>
			</item>
	<item>
		<title>Recovering Agile Projects</title>
		<description>Over the years I've been part of many recovery projects. What I mean by "recovery project" is usually a project-inside-a-project that is started when the original project was clearly not going to meet its objectives.  Each project fails in a unique way, but often failure is characterised by not ...</description>
		<link>http://fragmental.tw/2010/05/08/recovering-agile-projects/</link>
			</item>
	<item>
		<title>Nevermind Domain-Driven Design</title>
		<description>Over the past years I've held many workshops on Domain-Driven Design. We had more than one hundred people on those sessions, and feedback was often pretty good. After my last run I told my business partner that this was my last time running those workshops. 

I think that Domain-Driven Design ...</description>
		<link>http://fragmental.tw/2010/03/22/nevermind-domain-driven-design/</link>
			</item>
	<item>
		<title>Everyday Tales: Anatomy of a Refactoring – Part 3</title>
		<description>We finished last post with this funny situation: the abstraction that represents Facebook depends on our Domain Model.
 


It was a bit obvious that what we needed was not only system abstractions for Facebook, Twitter and the like but Bounded Contexts. We need to acknowledge the fact that these domains ...</description>
		<link>http://fragmental.tw/2010/03/10/everyday-tales-anatomy-of-a-refactoring-%e2%80%93-part-3/</link>
			</item>
	<item>
		<title>Everyday Tales: Anatomy of a Refactoring – Part 2</title>
		<description>Read the first post here.

In the previous post we were facing the problem demonstrated by the diagram below.



Our FacebookMessageParser needs an instance of AllSocialNetworks so that it can create valid Users coming from Facebook. The only implementation we have for the AllSocialNetworks interface is UserRepository, and this implementation needs a ...</description>
		<link>http://fragmental.tw/2010/03/10/everyday-tales-anatomy-of-a-refactoring-%e2%80%93-part-2/</link>
			</item>
</channel>
</rss>
