http://blog.opendns.com/2006/06/28/dns-is-the-next-acronym/ Making the Internet safer and faster Wed, 19 Nov 2008 12:01:08 +0000 http://wordpress.org/?v=2.2.2 http://blog.opendns.com/2006/06/28/dns-is-the-next-acronym/#comment-30286 Paul Ding Mon, 23 Apr 2007 12:02:58 +0000 http://blog.opendns.com/2006/06/28/dns-is-the-next-acronym/#comment-30286 I thought you should know that your "What OpenDNS does" link is worthless - the page it points to requires username and password to access. I thought you should know that your “What OpenDNS does” link is worthless - the page it points to requires username and password to access.

]]> http://blog.opendns.com/2006/06/28/dns-is-the-next-acronym/#comment-30225 Shortcuts | clock — watching time, the only true currency Mon, 23 Apr 2007 06:08:01 +0000 http://blog.opendns.com/2006/06/28/dns-is-the-next-acronym/#comment-30225 [...] power of DNS just got a lot easier to explain. Sure, you don’t need to care about DNS itself, but [...] […] power of DNS just got a lot easier to explain. Sure, you don’t need to care about DNS itself, but […]

]]> http://blog.opendns.com/2006/06/28/dns-is-the-next-acronym/#comment-100 clock — watching time, the only true currency » » Why I left CNET Wed, 19 Jul 2006 04:25:29 +0000 http://blog.opendns.com/2006/06/28/dns-is-the-next-acronym/#comment-100 [...] Second, David got me energized about the opportunity in DNS, and the chance to be a big part of making something small into something very big. It’s a chance, not a right or a guarantee. It was time for me to put my shoulder into something where I could feel the organization move every time. I met the team, and I liked both the people and the ratio: six engineers or web developers to one wanna-be geek (me). [...] […] Second, David got me energized about the opportunity in DNS, and the chance to be a big part of making something small into something very big. It’s a chance, not a right or a guarantee. It was time for me to put my shoulder into something where I could feel the organization move every time. I met the team, and I liked both the people and the ratio: six engineers or web developers to one wanna-be geek (me). […]

]]>