With all of the forms of instant communication (or instant interruption) at our fingertips, this article struck a chord for me. Email, instant messaging, social networks, and text messaging sometimes seem like they’re all determined to prevent us from actually getting anything accomplished during the day.

Read this article and share your thoughts in the comments below. How do you keep control of your attention and prevent the interruptions from owning you?

http://www.internetnews.com/commentary/print.php/3793561

This post is going to deviate a bit from the technical realm but I just read a report in the latest HOW Design magazine that was based on a recent survey of designers’ rates. One of the questions in the survey asked whether designers disclose their hourly rates to their clients.

The question, as written, seemed odd to me until I realized what they were getting at. This is how they should have asked the question: Do you bill your clients by the hour or do you provide a fixed-fee estimate?

I was disappointed to read that the majority of survey respondents bill hourly for their work.

Read the rest of this entry »

When I began freelancing I thought it was important to make my fledgling business appear bigger and more established than it really was. My website used phrases like “our designers” and “our programmers” in an effort to make a one-man show look like a full team of professionals. No matter what a potential client wanted I felt the need to make them believe I had all of the resources to do it.

Read the rest of this entry »

I just read an interesting article on the Advertising Age website. The author, Phil Johnson, talks about the trend toward agencies wanting to incorporate more interactive capabilities and provides some insights from his own efforts.

Read the rest of this entry »

My company recently began releasing updates to our content management system on an almost-weekly basis. Previously our approach was to determine which features should be included in the next release, compute a timeline appropriate for the requirements, and then get to work. Most of our timelines were at least a month long, while some approached 2 or 3 months.

Our new approach, inspired in part by the open source community’s “release early, release often” mantra, involves setting a regular release schedule (weekly in our case) and then prioritizing the features into these weekly buckets. Our goal is to deliver “business value” each week in some way. If a desired feature can’t be built in one week, we find a way to break it into smaller portions that can each be done within one week.

Read the rest of this entry »