<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.ocricket.com/~d/styles/itemcontent.css"?><rss 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/" version="2.0">

<channel>
	<title>oTeam of 11</title>
	
	<link>http://11.ocricket.com</link>
	<description>Buzz, Photography, Tech-Talks, News from the oTeam of oCricket</description>
	<lastBuildDate>Mon, 18 May 2009 08:49:00 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.ocricket.com/oCricket-11" /><feedburner:info xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" uri="ocricket-11" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><item>
		<title>Elastic Load Balancing, Auto Scaling, and Amazon CloudWatch</title>
		<link>http://11.ocricket.com/elastic-load-balancing-auto-scaling-and-amazon-cloudwatch/</link>
		<comments>http://11.ocricket.com/elastic-load-balancing-auto-scaling-and-amazon-cloudwatch/#comments</comments>
		<pubDate>Mon, 18 May 2009 08:48:58 +0000</pubDate>
		<dc:creator>Brajeshwar</dc:creator>
				<category><![CDATA[Technology]]></category>

		<guid isPermaLink="false">http://11.ocricket.com/?p=194</guid>
		<description><![CDATA[The load balancing, auto scaling, and cloud monitoring features are now available for Amazon AWS. The features work together to help you to build highly scalable and highly available applications. Amazon CloudWatch monitors your Amazon EC2 capacity, Auto Scaling dynamically scales it based on demand, and Elastic Load Balancing distributes load across multiple instances in [...]]]></description>
			<content:encoded><![CDATA[<p>The load balancing, auto scaling, and cloud monitoring features are now available for Amazon <span class="caps">AWS.</span> The features work together to help you to build highly scalable and highly available applications. Amazon CloudWatch monitors your Amazon <span class="caps">EC2 </span>capacity, Auto Scaling dynamically scales it based on demand, and Elastic Load Balancing distributes load across multiple instances in one or more Availability Zones.</p>

<p>The measurements collected by Amazon CloudWatch provide Auto Scaling with the information needed to run enough Amazon <span class="caps">EC2 </span>instances to deal with the traffic load. Auto Scaling updates the Elastic Load Balancing service when new instances are launched or terminated to automatically scale the load-balanced capacity. You can instantiate, configure, and deploy these important system architecture components in seconds.</p>

<p>Read more of the article &#8211; <a href="http://aws.typepad.com/aws/2009/05/new-aws-load-balancing-automatic-scaling-and-cloud-monitoring-services.html">New Features for Amazon <span class="caps">EC2</span>: Elastic Load Balancing, Auto Scaling, and Amazon CloudWatch</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://11.ocricket.com/elastic-load-balancing-auto-scaling-and-amazon-cloudwatch/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Django Best Practices</title>
		<link>http://11.ocricket.com/django-best-practices/</link>
		<comments>http://11.ocricket.com/django-best-practices/#comments</comments>
		<pubDate>Fri, 10 Apr 2009 05:44:45 +0000</pubDate>
		<dc:creator>Brajeshwar</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[Django]]></category>

		<guid isPermaLink="false">http://11.ocricket.com/?p=192</guid>
		<description><![CDATA[&#8220;This is a living document of best practices in developing and deploying with the Django Web framework. These should not be seen as the right way or the only way to work with Django, but instead best practices we&#8217;ve honed after years of working with the framework.&#8221;

Read the article in full &#8211; Django Best Practices.]]></description>
			<content:encoded><![CDATA[<p>&#8220;This is a living document of best practices in developing and deploying with the Django Web framework. These should not be seen as the right way or the only way to work with Django, but instead best practices we&#8217;ve honed after years of working with the framework.&#8221;</p>

<p>Read the article in full &#8211; <a href="http://lincolnloop.com/django-best-practices/">Django Best Practices</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://11.ocricket.com/django-best-practices/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Amazon Elastic MapReduce</title>
		<link>http://11.ocricket.com/amazon-elastic-mapreduce/</link>
		<comments>http://11.ocricket.com/amazon-elastic-mapreduce/#comments</comments>
		<pubDate>Thu, 02 Apr 2009 10:24:49 +0000</pubDate>
		<dc:creator>Brajeshwar</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[Amazon]]></category>
		<category><![CDATA[AWS]]></category>

		<guid isPermaLink="false">http://11.ocricket.com/?p=190</guid>
		<description><![CDATA[Hadoop as a service. Basically a web based GUI around Hadoop &#8211; you could roll this yourself on EC2 but for a small markup on regular EC2 prices you get to avoid the extra work setting everything up. Data processing scripts can be written in Java, Ruby, Perl, Python, PHP, R, or C++ and are [...]]]></description>
			<content:encoded><![CDATA[<p>Hadoop as a service. Basically a web based <span class="caps">GUI </span>around Hadoop &#8211; you could roll this yourself on <span class="caps">EC2 </span>but for a small markup on regular <span class="caps">EC2 </span>prices you get to avoid the extra work setting everything up. Data processing scripts can be written in Java, Ruby, Perl, Python, <span class="caps">PHP,</span> R, or C++ and are loaded in to S3 before firing off the job.</p>

<p>Check out <a href="http://aws.amazon.com/elasticmapreduce/">Amazon Elastic MapReduce</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://11.ocricket.com/amazon-elastic-mapreduce/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Real World Django</title>
		<link>http://11.ocricket.com/real-world-django/</link>
		<comments>http://11.ocricket.com/real-world-django/#comments</comments>
		<pubDate>Sat, 28 Mar 2009 18:15:50 +0000</pubDate>
		<dc:creator>Brajeshwar</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[Django]]></category>
		<category><![CDATA[Python]]></category>

		<guid isPermaLink="false">http://11.ocricket.com/?p=188</guid>
		<description><![CDATA[There&#8217;s plenty of material (documentation, blogs, books) out there that&#8217;ll help you write a site using Django&#8230; but then what? You&#8217;ve still got to test, deploy, monitor, and tune the site; failure at deployment time means all your beautiful code is for naught.

Read Read World Django as it unfolds the tutorial which examines how best [...]]]></description>
			<content:encoded><![CDATA[<p>There&#8217;s plenty of material (documentation, blogs, books) out there that&#8217;ll help you write a site using Django&#8230; but then what? You&#8217;ve still got to test, deploy, monitor, and tune the site; failure at deployment time means all your beautiful code is for naught.</p>

<p>Read <a href="http://jacobian.org/speaking/2009/real-world-django/">Read World Django</a> as it unfolds the tutorial which examines how best to cope when the Real World intrudes on your carefully designed website.</p>]]></content:encoded>
			<wfw:commentRss>http://11.ocricket.com/real-world-django/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Washington Times releases open source projects</title>
		<link>http://11.ocricket.com/washington-times-releases-open-source-projects/</link>
		<comments>http://11.ocricket.com/washington-times-releases-open-source-projects/#comments</comments>
		<pubDate>Fri, 20 Feb 2009 07:16:30 +0000</pubDate>
		<dc:creator>Brajeshwar</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[Django]]></category>
		<category><![CDATA[Open Source]]></category>
		<category><![CDATA[Python]]></category>
		<category><![CDATA[Times]]></category>
		<category><![CDATA[Washington]]></category>

		<guid isPermaLink="false">http://11.ocricket.com/?p=184</guid>
		<description><![CDATA[The Washington Times has released few open source projects. Visit Washington Times Open Source for more.

The Washington Times has used open source projects for some time now. All of our servers run Ubuntu linux. Our database servers use PostgreSQL. Our web servers use lighttpd and Apache httpd, and memcached. We develop entirely in python, using [...]]]></description>
			<content:encoded><![CDATA[<p>The Washington Times has released few open source projects. Visit <a href="http://opensource.washingtontimes.com/">Washington Times Open Source</a> for more.</p>

<blockquote>The Washington Times has used open source projects for some time now. All of our servers run <a href="http://www.ubuntu.com/">Ubuntu</a> linux. Our database servers use <a href="http://www.postgresql.org/">PostgreSQL</a>. Our web servers use <a href="http://www.lighttpd.net/">lighttpd</a> and <a href="http://httpd.apache.org/">Apache httpd</a>, and <a href="http://www.danga.com/memcached/">memcached</a>. We develop entirely in <a href="http://www.python.org/">python</a>, using the <a href="http://www.djangoproject.com/">django framework</a>. We are obviously strong believers in open source.</blockquote>]]></content:encoded>
			<wfw:commentRss>http://11.ocricket.com/washington-times-releases-open-source-projects/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Rails versus Django</title>
		<link>http://11.ocricket.com/rails-versus-django/</link>
		<comments>http://11.ocricket.com/rails-versus-django/#comments</comments>
		<pubDate>Wed, 11 Feb 2009 10:01:53 +0000</pubDate>
		<dc:creator>Brajeshwar</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[Django]]></category>
		<category><![CDATA[Python]]></category>
		<category><![CDATA[Rails]]></category>
		<category><![CDATA[Ruby]]></category>

		<guid isPermaLink="false">http://11.ocricket.com/?p=182</guid>
		<description><![CDATA[&#8220;These are the sorts of differences seen in both stacks. They are common, and commonly pivotal to arguments comparing the two frameworks. Proponents of one framework typically argue one way &#8216;because it is the way decreed by our language authors&#8217;. So really you&#8217;re looking at which language you prefer.&#8221;

(Via: SuperJared)]]></description>
			<content:encoded><![CDATA[<p>&#8220;These are the sorts of differences seen in both stacks. They are common, and commonly pivotal to arguments comparing the two frameworks. Proponents of one framework typically argue one way &#8216;because it is the way decreed by our language authors&#8217;. So really you&#8217;re looking at which language you prefer.&#8221;</p>

<p>(Via: <a href="http://superjared.com/entry/rails-versus-django/">SuperJared</a>)</p>]]></content:encoded>
			<wfw:commentRss>http://11.ocricket.com/rails-versus-django/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Amazon opens up its Flexible Payments Service</title>
		<link>http://11.ocricket.com/amazon-opens-up-its-flexible-payments-service/</link>
		<comments>http://11.ocricket.com/amazon-opens-up-its-flexible-payments-service/#comments</comments>
		<pubDate>Fri, 06 Feb 2009 06:27:17 +0000</pubDate>
		<dc:creator>Atif</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[Amazon]]></category>
		<category><![CDATA[AWS]]></category>
		<category><![CDATA[Devpay]]></category>

		<guid isPermaLink="false">http://11.ocricket.com/?p=178</guid>
		<description><![CDATA[TechFlash report a good news of Amazon opening up its Flexible Payment Service to everyone.Amazon charges fees for use of Flexible Payments Service. As part of today&#8217;s rollout, however, Amazon is offering developers who sign up for Flexible Payments by March 15 &#8212; and launch their application by June 1 &#8212; free payment processing for [...]]]></description>
			<content:encoded><![CDATA[<p>TechFlash report a good news of Amazon <a href="http://www.techflash.com/Amazon_opens_up_payments_platform_to_all_developers39155007.html">opening up its Flexible Payment Service</a> to everyone.<span id="more-178"></span>Amazon charges fees for use of <a href="http://aws.amazon.com/fps/">Flexible Payments Service</a>. As part of today&#8217;s rollout, however, Amazon is offering developers who sign up for Flexible Payments by March 15 &#8212; and launch their application by June 1 &#8212; free payment processing for the first 90 days, until their transaction volume reaches $500,000.</p>]]></content:encoded>
			<wfw:commentRss>http://11.ocricket.com/amazon-opens-up-its-flexible-payments-service/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Managers’ Deadlines vs. Developers’ Estimates</title>
		<link>http://11.ocricket.com/managers-deadlines-vs-developers-estimates/</link>
		<comments>http://11.ocricket.com/managers-deadlines-vs-developers-estimates/#comments</comments>
		<pubDate>Thu, 05 Feb 2009 09:06:25 +0000</pubDate>
		<dc:creator>Brajeshwar</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[Management]]></category>
		<category><![CDATA[Designers]]></category>
		<category><![CDATA[Developers]]></category>
		<category><![CDATA[Estimates]]></category>
		<category><![CDATA[Manager]]></category>

		<guid isPermaLink="false">http://11.ocricket.com/?p=174</guid>
		<description><![CDATA[Deadlines come from external sources, for example, &#8220;Feature X needs to be ready for the summer trade show&#8221;.
Estimates come from internal sources, for example, &#8220;Feature X will take me N weeks to complete&#8221;.Hackification hints to few steps to ease the situation where the deadline is shorter than the estimate;

Managers



Let the person doing the work create [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Deadlines</strong> come from external sources, for example, &#8220;Feature X needs to be ready for the summer trade show&#8221;.<br />
<strong>Estimates</strong> come from internal sources, for example, &#8220;Feature X will take me N weeks to complete&#8221;.<span id="more-174"></span><a href="http://www.hackification.com/2009/02/02/deadlines-vs-estimates/">Hackification</a> hints to few steps to ease the situation where the deadline is shorter than the estimate;</p>

<p><strong>Managers</strong></p>


<ul>
<li>Let the person doing the work create the estimate.</li>
<li>Don&#8217;t override an estimate with a deadline.</li>
</ul>



<p><strong>Developers</strong></p>


<ul>
<li>Respect for your estimates only flows from accurate estimates.</li>
<li>Accurate estimates come from tiny tasks.</li>
<li>Review your estimates after the event.</li>
</ul>



<p><strong>Marketing</strong></p>


<ul>
<li>Explain the reason for the deadline</li>
</ul>



<p>Read the article in full at <a href="http://www.hackification.com/2009/02/02/deadlines-vs-estimates/">Hackification</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://11.ocricket.com/managers-deadlines-vs-developers-estimates/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Typogrify: easily produce web typography that doesn’t suck</title>
		<link>http://11.ocricket.com/typogrify-easily-produce-web-typography-that-doesnt-suck/</link>
		<comments>http://11.ocricket.com/typogrify-easily-produce-web-typography-that-doesnt-suck/#comments</comments>
		<pubDate>Wed, 28 Jan 2009 07:25:01 +0000</pubDate>
		<dc:creator>Brajeshwar</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[Fonts]]></category>
		<category><![CDATA[Texts]]></category>
		<category><![CDATA[Typography]]></category>
		<category><![CDATA[Typogrify]]></category>

		<guid isPermaLink="false">http://11.ocricket.com/?p=172</guid>
		<description><![CDATA[Typogrify is a collection of Django template filters that help prettify your web typography by preventing ugly quotes and widows and providing CSS hooks to style some special cases. Read more about Typogrify from Jeff Croft.]]></description>
			<content:encoded><![CDATA[<p><a href="http://code.google.com/p/typogrify/">Typogrify</a> is a collection of Django template filters that help prettify your web typography by preventing ugly quotes and widows and providing <span class="caps">CSS </span>hooks to style some special cases. Read more about Typogrify from <a href="http://jeffcroft.com/sidenotes/2007/may/29/typogrify-easily-produce-web-typography-doesnt-suc/">Jeff Croft</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://11.ocricket.com/typogrify-easily-produce-web-typography-that-doesnt-suck/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>100% on Amazon Web Services: Soocial.com</title>
		<link>http://11.ocricket.com/100-on-amazon-web-services-soocialcom/</link>
		<comments>http://11.ocricket.com/100-on-amazon-web-services-soocialcom/#comments</comments>
		<pubDate>Mon, 12 Jan 2009 09:04:44 +0000</pubDate>
		<dc:creator>Brajeshwar</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[Amazon]]></category>
		<category><![CDATA[AWS]]></category>
		<category><![CDATA[S3]]></category>
		<category><![CDATA[Soocial]]></category>

		<guid isPermaLink="false">http://11.ocricket.com/?p=170</guid>
		<description><![CDATA[Soocial Web application: Nginx running behind an Elastic IP, proxying the request to an HAProxy on every &#8220;webapp&#8221; instance, each of which has its own memcache server (they don&#8217;t need to explicitly expire the cache). The reason they use Nginx is to supply SSL support, if HAproxy would do SSL they probably wouldn&#8217;t be using [...]]]></description>
			<content:encoded><![CDATA[<p>Soocial Web application: Nginx running behind an Elastic <span class="caps">IP, </span>proxying the request to an <span class="caps">HAP</span>roxy on every &#8220;webapp&#8221; instance, each of which has its own memcache server (they don&#8217;t need to explicitly expire the cache). The reason they use Nginx is to supply <span class="caps">SSL </span>support, if HAproxy would do <span class="caps">SSL </span>they probably wouldn&#8217;t be using Nginx.</p>

<p>Via <a href="http://aws.typepad.com/aws/2008/12/running-everything-on-aws-soocialcom.html"><span class="caps">AWS</span> Blog</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://11.ocricket.com/100-on-amazon-web-services-soocialcom/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Python 3.0 released</title>
		<link>http://11.ocricket.com/python-30-released/</link>
		<comments>http://11.ocricket.com/python-30-released/#comments</comments>
		<pubDate>Thu, 04 Dec 2008 06:20:36 +0000</pubDate>
		<dc:creator>Harsh</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[Python]]></category>
		<category><![CDATA[Technology]]></category>

		<guid isPermaLink="false">http://11.ocricket.com/?p=168</guid>
		<description><![CDATA[Python 3.0 (a.k.a. &#8220;Python 3000&#8243; or &#8220;Py3k&#8221;) is a new version of the language that is incompatible with the 2.x line of releases. The language is mostly the same, but many details, especially how built-in objects like dictionaries and strings work, have changed considerably, and a lot of deprecated features have finally been removed. Also, [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.python.org/download/releases/3.0/">Python 3.0</a> (a.k.a. &#8220;Python 3000&#8243; or &#8220;Py3k&#8221;) is a new version of the language that is incompatible with the 2.x line of releases. The language is mostly the same, but many details, especially how built-in objects like dictionaries and strings work, have changed considerably, and a lot of deprecated features have finally been removed. Also, the standard library has been reorganized in a few prominent places.</p>]]></content:encoded>
			<wfw:commentRss>http://11.ocricket.com/python-30-released/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
