<?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="https://twitter.com/AmeliaKallman/status/905016972362084352/photo/1"/>
	<rdf:li rdf:resource="http://google.github.io/styleguide/javaguide.html"/>
	<rdf:li rdf:resource="http://ben-evans.com/benedictevans/2014/6/4/digesting-wwdc-cloudy"/>
	<rdf:li rdf:resource="http://www.20thingsilearned.com/what-is-the-internet/"/>
	<rdf:li rdf:resource="http://www.google.com/transparencyreport/"/>
	<rdf:li rdf:resource="http://code.google.com/webtoolkit/articles/mvp-architecture.html"/>
	<rdf:li rdf:resource="http://edition.cnn.com/2010/TECH/04/22/facebook.won.the.web.cashmore/index.html"/>
	<rdf:li rdf:resource="http://googleblog.blogspot.com/2010/03/new-approach-to-china-update.html?utm_source=feedburner&amp;utm_medium=feed&amp;utm_campaign=Feed%3A+blogspot%2FMKuf+%28Official+Google+Blog%29&amp;utm_content=Google+Reader"/>
	<rdf:li rdf:resource="http://www.nytimes.com/2010/03/14/technology/14brawl.html"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://twitter.com/AmeliaKallman/status/905016972362084352/photo/1">
    <title>Twitter</title>
    <dc:date>2017-11-05T18:53:38+00:00</dc:date>
    <link>https://twitter.com/AmeliaKallman/status/905016972362084352/photo/1</link>
    <dc:creator>DennisLaumen</dc:creator><description><![CDATA[RT @AmeliaKallman: This pretty much sums up the current state of #Data #DisruptionSummit #Google ]]></description>
<dc:subject>Data DisruptionSummit Google</dc:subject>
<dc:source>https://twitter.com/</dc:source>
<dc:identifier>https://pinboard.in/u:DennisLaumen/b:6a73c96172b9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:Data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:DisruptionSummit"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:Google"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://google.github.io/styleguide/javaguide.html">
    <title>Google Java Style</title>
    <dc:date>2015-09-28T07:27:37+00:00</dc:date>
    <link>http://google.github.io/styleguide/javaguide.html</link>
    <dc:creator>DennisLaumen</dc:creator><description><![CDATA[This document serves as the complete definition of Google's coding standards for source code in the Java™ Programming Language. A Java source file is described as being in Google Style if and only if it adheres to the rules herein.

Like other programming style guides, the issues covered span not only aesthetic issues of formatting, but other types of conventions or coding standards as well. However, this document focuses primarily on the hard-and-fast rules that we follow universally, and avoids giving advice that isn't clearly enforceable (whether by human or tool).]]></description>
<dc:subject>google java</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:DennisLaumen/b:bf5553db4f6f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:java"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://ben-evans.com/benedictevans/2014/6/4/digesting-wwdc-cloudy">
    <title>Digesting WWDC: cloudy</title>
    <dc:date>2014-06-06T05:17:50+00:00</dc:date>
    <link>http://ben-evans.com/benedictevans/2014/6/4/digesting-wwdc-cloudy</link>
    <dc:creator>DennisLaumen</dc:creator><description><![CDATA[I’ve spent the last couple of days sifting through the announcements at WWDC. Apple claims 4000 new APIs, and it certainly feels like it. Apple has been busy. But setting aside all the normal incremental improvements, there are a couple of interesting strands.]]></description>
<dc:subject>apple wwdc google</dc:subject>
<dc:source>https://twitter.com/</dc:source>
<dc:identifier>https://pinboard.in/u:DennisLaumen/b:f27c23b2fcde/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:apple"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:wwdc"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:google"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.20thingsilearned.com/what-is-the-internet/">
    <title>20 Things I Learned About Browsers and the Web</title>
    <dc:date>2010-11-18T20:53:18+00:00</dc:date>
    <link>http://www.20thingsilearned.com/what-is-the-internet/</link>
    <dc:creator>DennisLaumen</dc:creator><description><![CDATA[What is the Internet, exactly? To some of us, the Internet is where we stay in touch with friends, get the news, shop, and play games. To some others, the Internet can mean their local broadband providers, or the underground wires and fiber-optic cables that

carry data back and forth across cities and oceans. Who is right?]]></description>
<dc:subject>google web browsers</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:DennisLaumen/b:67a68d782d49/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:browsers"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.google.com/transparencyreport/">
    <title>Google Transparency Report</title>
    <dc:date>2010-09-21T11:25:32+00:00</dc:date>
    <link>http://www.google.com/transparencyreport/</link>
    <dc:creator>DennisLaumen</dc:creator><description><![CDATA[Transparency is a core value at Google. As a company we feel it is our responsibility to ensure that we maximize transparency around the flow of information related to our tools and services. We believe that more information means more choice, more freedom and ultimately more power for the individual.

We’ve created an interactive map of Government Requests that shows the number of government inquiries for information about users and requests for Google to take down or censor content. We hope this step toward greater transparency will help in ongoing discussions about the appropriate scope and authority of government requests.

Our interactive Traffic graphs provide information about traffic to Google services around the world. Each graph shows historic traffic patterns for a given country/region and service. By illustrating outages, this tool visualizes disruptions in the free flow of information, whether it's a government blocking information or a cable being cut. We hope this raw data will help facilitate studies about service outages and disruptions.]]></description>
<dc:subject>google privacy internet transparency</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:DennisLaumen/b:c58ada5722d7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:privacy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:internet"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:transparency"/>
</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>
<item rdf:about="http://edition.cnn.com/2010/TECH/04/22/facebook.won.the.web.cashmore/index.html">
    <title>How Facebook won the web</title>
    <dc:date>2010-04-23T07:27:02+00:00</dc:date>
    <link>http://edition.cnn.com/2010/TECH/04/22/facebook.won.the.web.cashmore/index.html</link>
    <dc:creator>DennisLaumen</dc:creator><description><![CDATA[London, England (CNN) -- Facebook this week announced a new way to express your interests -- a "Like" button that's set to appear all around the web. Click the button, and the Web page is shared with your friends.
What's more, every "Like" you submit ensures Facebook (and its partner sites) can deliver a more personalized experience to you.
It's a simple yet powerful feature -- one that delivers a significant blow to rival Twitter. Once the network effects take hold, it's frankly hard to imagine how any company could unseat Facebook's social networking dominance in the months to come. Without a counterattack, even Google may one day be dethroned.]]></description>
<dc:subject>facebook twitter google web</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:DennisLaumen/b:59d3689d20b5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:facebook"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:twitter"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:web"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://googleblog.blogspot.com/2010/03/new-approach-to-china-update.html?utm_source=feedburner&amp;utm_medium=feed&amp;utm_campaign=Feed%3A+blogspot%2FMKuf+%28Official+Google+Blog%29&amp;utm_content=Google+Reader">
    <title>A new approach to China: an update</title>
    <dc:date>2010-03-22T19:48:37+00:00</dc:date>
    <link>http://googleblog.blogspot.com/2010/03/new-approach-to-china-update.html?utm_source=feedburner&amp;utm_medium=feed&amp;utm_campaign=Feed%3A+blogspot%2FMKuf+%28Official+Google+Blog%29&amp;utm_content=Google+Reader</link>
    <dc:creator>DennisLaumen</dc:creator><description><![CDATA[So earlier today we stopped censoring our search services—Google Search, Google News, and Google Images—on Google.cn. Users visiting Google.cn are now being redirected to Google.com.hk, where we are offering uncensored search in simplified Chinese, specifically designed for users in mainland China and delivered via our servers in Hong Kong. Users in Hong Kong will continue to receive their existing uncensored, traditional Chinese service, also from Google.com.hk. Due to the increased load on our Hong Kong servers and the complicated nature of these changes, users may see some slowdown in service or find some products temporarily inaccessible as we switch everything over. ]]></description>
<dc:subject>google china</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:DennisLaumen/b:08f02068f4c1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:china"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.nytimes.com/2010/03/14/technology/14brawl.html">
    <title>Apple’s Spat With Google Is Getting Personal</title>
    <dc:date>2010-03-15T17:19:50+00:00</dc:date>
    <link>http://www.nytimes.com/2010/03/14/technology/14brawl.html</link>
    <dc:creator>DennisLaumen</dc:creator><description><![CDATA[Today, such warmth is in short supply. Mr. Jobs, Mr. Schmidt and their companies are now engaged in a gritty battle royale over the future and shape of mobile computing and cellphones, with implications that are reverberating across the digital landscape.]]></description>
<dc:subject>apple google ericschmidt stevejobs htc</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:DennisLaumen/b:4bb20c5801d2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:apple"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:ericschmidt"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:stevejobs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:DennisLaumen/t:htc"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>