<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Tracking Down A Subtle Analytics Bug</title>
	<atom:link href="http://www.kalzumeus.com/2009/10/31/subtle-analytics-bu/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.kalzumeus.com/2009/10/31/subtle-analytics-bu/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=subtle-analytics-bu</link>
	<description>Patrick McKenzie (patio11) blogs on software development, marketing, and general business topics</description>
	<lastBuildDate>Sat, 11 Feb 2012 04:17:24 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Kevin</title>
		<link>http://www.kalzumeus.com/2009/10/31/subtle-analytics-bu/#comment-2143</link>
		<dc:creator>Kevin</dc:creator>
		<pubDate>Mon, 02 Nov 2009 18:09:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.kalzumeus.com/?p=739#comment-2143</guid>
		<description>Why are you using a random function to create an ID? The chances of getting a duplicate ID when programmed correctly are slim, but there is definitely still a chance. You don&#039;t want to leave anything in your code up to chance. Keep in mind Murphy&#039;s Law (http://en.wikipedia.org/wiki/Murphy&#039;s_law)

You should be using an auto-increment scheme instead. If a user signs up, she gets the next ID in line. Say you have 11,098 users. The newest one will have an ID of 11099. This guarantees there will never be a duplicated ID for anything.</description>
		<content:encoded><![CDATA[<p>Why are you using a random function to create an ID? The chances of getting a duplicate ID when programmed correctly are slim, but there is definitely still a chance. You don&#8217;t want to leave anything in your code up to chance. Keep in mind Murphy&#8217;s Law (<a href="http://en.wikipedia.org/wiki/Murphy&#039;s_law" rel="nofollow">http://en.wikipedia.org/wiki/Murphy&#039;s_law</a>)</p>
<p>You should be using an auto-increment scheme instead. If a user signs up, she gets the next ID in line. Say you have 11,098 users. The newest one will have an ID of 11099. This guarantees there will never be a duplicated ID for anything.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Baruch</title>
		<link>http://www.kalzumeus.com/2009/10/31/subtle-analytics-bu/#comment-2142</link>
		<dc:creator>Baruch</dc:creator>
		<pubDate>Sun, 01 Nov 2009 14:39:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.kalzumeus.com/?p=739#comment-2142</guid>
		<description>Using srand/rand is not a good idea anyway, normal programming languages will have an object encapsulating the random function so that it can be localized to a user/need. In this way your login id would have one random sequence and a user would get another sequence.</description>
		<content:encoded><![CDATA[<p>Using srand/rand is not a good idea anyway, normal programming languages will have an object encapsulating the random function so that it can be localized to a user/need. In this way your login id would have one random sequence and a user would get another sequence.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

