<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Web 2.0 on Bulrush Labs — Richard Tibbetts</title><link>https://bulrushlabs.com/articles/tag/web-2.0/</link><description>Recent content in Web 2.0 on Bulrush Labs — Richard Tibbetts</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 06 Dec 2010 02:17:00 +0000</lastBuildDate><atom:link href="https://bulrushlabs.com/articles/tag/web-2.0/index.xml" rel="self" type="application/rss+xml"/><item><title>Yes Virginia, You Can Work on Great Technology at Startups</title><link>https://bulrushlabs.com/articles/2010/12/06/yes-virginia-you-can-work-on-great-technology-at-startups/</link><pubDate>Mon, 06 Dec 2010 02:17:00 +0000</pubDate><guid>https://bulrushlabs.com/articles/2010/12/06/yes-virginia-you-can-work-on-great-technology-at-startups/</guid><description>&lt;p&gt;You can work on great technology at startups. You wouldn’t think that would be a controversial statement. But it is if you believe Ted Tso’s defense of Google, &lt;a href="http://thunk.org/tytso/blog/2010/11/29/google-has-a-problem-retaining-great-engineers-bullcrap/"&gt;“Google has a problem retaining great engineers? Bullcrap.”&lt;/a&gt; Ted dismisses the engineering that goes on in a startup, saying:&lt;/p&gt;&#10;&lt;p&gt;&lt;em&gt;Similarly, you don’t work on great technology at a startup.  Startups, by and large, aren’t about technology — at least, not the Web 2.0 startups like Facebook, Foursquare, Twitter, Groupon, etc.   They are about business model discovery.  So if you are fundamentally a technologist at heart, whose heart sings when you’re making a better file system, or fixing a kernel bug, you’re not going to be happy at a startup.   At least, not if the startup is run competently.&lt;/em&gt;&lt;/p&gt;</description></item><item><title>Buy It Like You Mean It and Vendor Relationship Management</title><link>https://bulrushlabs.com/articles/2008/06/03/buy-it-like-you-mean-it-and-vendor-relationship-management/</link><pubDate>Tue, 03 Jun 2008 21:14:00 +0000</pubDate><guid>https://bulrushlabs.com/articles/2008/06/03/buy-it-like-you-mean-it-and-vendor-relationship-management/</guid><description>&lt;p&gt;I just got back from the launch party for &lt;a href="http://buyitlikeyoumeanit.org"&gt;Buy It Like You Mean It&lt;/a&gt;, a startup non-profit that is “enabling the socially conscious consumer”. I’m a big fan of what they are doing. As a free-market capitalist, I like to think that the power of markets can solve all kinds of problems. As a realist (and Wall Street technology vendor), I realize that market actors can have wildly different information and expertise.&lt;/p&gt;</description></item><item><title>Me.dium Beta</title><link>https://bulrushlabs.com/articles/2006/11/10/medium-beta/</link><pubDate>Fri, 10 Nov 2006 08:27:00 +0000</pubDate><guid>https://bulrushlabs.com/articles/2006/11/10/medium-beta/</guid><description>&lt;p&gt;I got invited into the Beta at &lt;a href="http://me.dium.com/"&gt;Me.dium&lt;/a&gt;, a new collaborative/social browsing system. It’s no dis-similar from the third-party-comments system I was pondering back in the spring, if anyone remembers that. However, rather than being focussed on comments, it is also focussed on real-time browsing. You get a side-bar that shows you what people are looking at. It also has a facility for inviting your friends and sharing browser state with your friends. If anyone is interested in an invitiation, let me know.&lt;/p&gt;</description></item><item><title>Book Review: Defensive Design for the Web</title><link>https://bulrushlabs.com/articles/2005/05/29/book-review-defensive-design-for-the-web/</link><pubDate>Sun, 29 May 2005 11:17:00 +0000</pubDate><guid>https://bulrushlabs.com/articles/2005/05/29/book-review-defensive-design-for-the-web/</guid><description>&lt;p&gt;&lt;a href="http://www.37signals.com"&gt;37 signal&lt;/a&gt; is one of the neatest&lt;br&gt;&#10;companies out there in terms of advancing the state of the art in web&lt;br&gt;&#10;design. It seems like they do almost as much as&lt;br&gt;&#10;href=”http://google.com”&amp;gt;Google, presumably without spending such&lt;br&gt;&#10;embarrassing amounts of money. If you haven’t check out some of their&lt;br&gt;&#10;projects, like &lt;a href="https://basecamp.com"&gt;Basecamp&lt;/a&gt;,&lt;br&gt;&#10;href=”http://www.tadalist.com/”&amp;gt;Ta-da Lists, and&lt;br&gt;&#10;href=”http://backpackit.com”&amp;gt;Backpack, you really should. They&lt;br&gt;&#10;build really nice web apps. Not only that, but they give back to the&lt;br&gt;&#10;community with things like&lt;br&gt;&#10;href=”http://www.37signals.com/svn/archives/000558.php”&amp;gt;the yellow&lt;br&gt;&#10;fade technique and a presentation on&lt;br&gt;&#10;href=”http://www.37signals.com/presentations/sxsw2005/37s-bigthingssmallteam.pdf”&amp;gt;How&lt;br&gt;&#10;to make big things happen with a small team (&lt;br&gt;&#10;href=”http://www.37signals.com/presentations/sxsw2005/37s-bigthingssmallteam.pdf”&amp;gt;slides)&lt;br&gt;&#10;(&lt;br&gt;&#10;href=”http://www.terrystorch.com/2005/03/sxsw_how_to_mak.html”&amp;gt;summary).&lt;/p&gt;</description></item><item><title>Setting up Typo: RubyOnRails, lighttpd, FastCGI and being a bad sysadmin</title><link>https://bulrushlabs.com/articles/2005/04/15/setting-up-typo-rubyonrails-lighttpd-fastcgi-and-being-a-bad-sysadmin/</link><pubDate>Fri, 15 Apr 2005 09:10:00 +0000</pubDate><guid>https://bulrushlabs.com/articles/2005/04/15/setting-up-typo-rubyonrails-lighttpd-fastcgi-and-being-a-bad-sysadmin/</guid><description>&lt;p&gt;I took most of my evening last night to set up FastCGI and &lt;a href="http://www.lighttpd.net/"&gt;lighttpd&lt;/a&gt;. My goal was to serve a &lt;a href="http://typo.leetsoft.com/"&gt;Typo&lt;/a&gt;, a blog engine based on &lt;a href="http://rubyonrails.org"&gt;RubyOnRails&lt;/a&gt;. I was thwarted by not knowing RubyOnRails very well, and by knowing FastCGI and lighttpd not at all.&lt;/p&gt;&#10;&lt;p&gt;The first issue was that Typo doesn’t like to run in a subdirectory on a webserver. That is, it wanted to be at &lt;code&gt;ntsh.innocuous.org/&lt;/code&gt;, not &lt;code&gt;innocuous.org/ntsh&lt;/code&gt;. This offended my sensibilities somewhat, so I decided to beat it into submisssion. This involved tracking down a bunch of places where paths were hard coded, which included a few places in the templates and the CSS.&lt;/p&gt;</description></item></channel></rss>