Anyway to kludge #googlebuzz into @Tweetie with an API root?
February 9th, 2010
Archive
Archive for the ‘web2.0’ Category
Snowy but safe landing at O’Hare
January 7th, 2010
Snowy but safe landing at O’Hare
January 7th, 2010
Notepod – great for iPhone app designers
September 27th, 2009
These iPhone/iPod touch looking notepads would be great for you iPhone app designers out there:
Why Your Next Website Should be Designed with Wireframes | Build Internet!
September 26th, 2009
Laying out a site in simplest terms makes focusing on the usability intuitive. With gray boxes representing complex elements, you’re less likely to get distracted by a visual nuance that might not even be in the final product.
Petabytes on a budget: How to build cheap cloud storage | Backblaze Blog
September 1st, 2009
Before realizing that we had to solve this storage problem ourselves, we considered Amazon S3, Dell or Sun Servers, NetApp Filers, EMC SAN, etc. As we investigated these traditional off-the-shelf solutions, we became increasingly disillusioned by the expense. When you strip away the marketing terms and fancy logos from any storage solution, data ends up on a hard drive. But when we priced various off-the-shelf solutions, the cost was 10 times as much or more than the raw hard drives. Here’s a comparison chart of the price for one petabyte from various venders:
via Petabytes on a budget: How to build cheap cloud storage | Backblaze Blog.
O’Reilly Meeting Guidelines
July 23rd, 2009
Before a meeting…
1. Clarify the purpose
2. Make sure you’ve got the right people and everyone is prepared.
3. Prepare outcomes and agenda in advance.
4. For problem-solving and decision making, prepare an assessment ahead of time and present your recommendation.
5. Create a ’strawman’ in advance to give people a place to start from.
During a meeting…
1. Start with a review of the outcomes and agenda.
Clarify the decision making process up-front.
2. Share responsibility for keeping the meeting focused and on track-anyone can call a ‘process check’
3. Document all key decisions and agreements.
Keep a running list of issues.
4. Solicit comments from those who haven’t spoken much.
After a meeting…
1. Review key decisions/agreements to make sure everyone leaves with the same understanding.
2. Assign next steps with due dates.
Rails Architecture Image
April 27th, 2009
JavaScriptDB: Persevere’s New High-Performance Storage Engine
April 22nd, 2009
The latest beta of Persevere features a new native object storage engine called JavaScriptDB that provides high-end scalability and performance. Persevere now outperforms the common PHP and MySQL combination for accessing data via HTTP by about 40% and outperforms CouchDB by 249%.
via SitePen Blog » JavaScriptDB: Persevere’s New High-Performance Storage Engin
Xmarks 3.0 – Now With Site Info built into the browser
April 14th, 2009
Click on the Xmarks info icon in your location bar to see detailed information about the site you are on, and discover other great sites just like it.
Here’s an example from my google reader page:
Creately – Create and Collaborate on Online Technical Diagrams
April 11th, 2009
- Easy and Intuitive Diagram Tool
- Smart user interface, quick start templates
- Access anywhere
- Draw Diagrams & Designs right in your browser.
- No Software Downloads. No Installs.
(Link: Creately – Create and Collaborate on Online Technical Diagrams)
Debugging Clever Code
April 11th, 2009
Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it.
From Brian Kernighan, quoted by Joe Maller via Debugging Clever Code.
Twitter the tide raises all shortening boats
April 11th, 2009
datamining.typepad.com carried out a simple experiment: grab a good chunk of Twitter data; pull out all the URLs, rank the domains and then track the trends in Compete.com. Below is the head of the list:
via Data Mining: Text Mining, Visualization and Social Media: Twitter the tide raises all boats.
Classic Mistakes Enumerated
April 10th, 2009
#18: Abandonment of planning under pressure. Projects make plans and then routinely abandon them when they run into schedule trouble (Humphrey 1989). The problem isn’t so much in abandoning the plan as in failing to create a substitute and then falling into code-and-fix mode instead. In Case Study 3-1, the team abandoned its plan after it missed its first delivery, and that’s typical. The result was that work after that point was uncoordinated and awkward–to the point that Jill even started working on a project for her old group part of the time and no one even knew it.
(Link: Classic Mistakes Enumerated)
