<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (DennisLaumen)</title>
    <link>https://pinboard.in/u:DennisLaumen/public/</link>
    <description>recent bookmarks from DennisLaumen</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="http://thinkrelevance.com/blog/2011/11/15/documenting-architecture-decisions"/>
	<rdf:li rdf:resource="http://branchandbound.net/blog/architecture/2015/06/on-microservices-monoliths-and-critical-thinking/"/>
	<rdf:li rdf:resource="http://martinfowler.com/eaaDev/SupervisingPresenter.html"/>
	<rdf:li rdf:resource="http://code.google.com/webtoolkit/articles/mvp-architecture.html"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="http://thinkrelevance.com/blog/2011/11/15/documenting-architecture-decisions">
    <title>Documenting Architecture Decisions</title>
    <dc:date>2016-06-14T12:17:47+00:00</dc:date>
    <link>http://thinkrelevance.com/blog/2011/11/15/documenting-architecture-decisions</link>
    <dc:creator>DennisLaumen</dc:creator><description><![CDATA[Architecture for agile projects has to be described and defined differently. Not all decisions will be made at once, nor will all of them be done when the project begins.

Agile methods are not opposed to documentation, only to valueless documentation. Documents that assist the team itself can have value, but only if they are kept up to date. Large documents are never kept up to date. Small, modular documents have at least a chance at being updated.

Nobody ever reads large documents, either. Most developers have been on at least one project where the specification document was larger (in bytes) than the total source code size. Those documents are too large to open, read, or update. Bite sized pieces are easier for for all stakeholders to consume.]]></description>
<dc:subject>architecture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:DennisLaumen/b:2b1ca583b722/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:architecture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://branchandbound.net/blog/architecture/2015/06/on-microservices-monoliths-and-critical-thinking/">
    <title>On monoliths, microservices and critical thinking - Branch and Bound</title>
    <dc:date>2015-06-10T13:04:05+00:00</dc:date>
    <link>http://branchandbound.net/blog/architecture/2015/06/on-microservices-monoliths-and-critical-thinking/</link>
    <dc:creator>DennisLaumen</dc:creator><description><![CDATA[RT @Sander_Mak: On monoliths, microservices and critical thinking:  #microservices #monoliths #architecture]]></description>
<dc:subject>architecture monoliths microservices</dc:subject>
<dc:source>https://twitter.com/</dc:source>
<dc:identifier>https://pinboard.in/u:DennisLaumen/b:ec6946ae47ce/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:monoliths"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:microservices"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://martinfowler.com/eaaDev/SupervisingPresenter.html">
    <title>Supervising Controller</title>
    <dc:date>2011-01-14T11:24:28+00:00</dc:date>
    <link>http://martinfowler.com/eaaDev/SupervisingPresenter.html</link>
    <dc:creator>DennisLaumen</dc:creator><description><![CDATA[Factor the UI into a view and controller where the view handles simple mapping to the underlying model and the the controller handles input response and complex view logic.]]></description>
<dc:subject>softwareengineering architecture userinterface</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:DennisLaumen/b:f95653c0666a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:softwareengineering"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:userinterface"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://code.google.com/webtoolkit/articles/mvp-architecture.html">
    <title>Google Web Toolkit: Large scale application development and MVP</title>
    <dc:date>2010-06-30T10:00:22+00:00</dc:date>
    <link>http://code.google.com/webtoolkit/articles/mvp-architecture.html</link>
    <dc:creator>DennisLaumen</dc:creator><description><![CDATA[Building any large scale application has its hurdles, and GWT apps are no exception. Multiple developers working simultaneously on the same code base, while maintaining legacy features and functionality, can quickly turn into messy code. To help sort things out we introduce design patterns to create compartmentalized areas of responsibility within our project.
There are various design patterns to choose from; Presentation-abstraction-control, Model-view-controller, Model-view-presenter, etc... And while each pattern has its benefits, we have found that a Model-view-presenter (MVP) architecture works best when developing GWT apps for two main reasons. First the MVP model, much like other design patterns, decouples development in a way that allows multiple developers to work simultaneously. Secondly, this model allows us to minimize our use of GWTTestCase and, for the bulk of our code, write lightweight (and fast) JRE tests.]]></description>
<dc:subject>gwt google java softwaredevelopment architecture modelviewpresenter</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:DennisLaumen/b:d3c3bf0ac9ec/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:gwt"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:java"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:softwaredevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:modelviewpresenter"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>