I have a job that is probably about 120 hours total work for a good Flash programmer. By that, I mean I estimate that you could probably do it in about 30 hours, but if you can deliver in 120, everyone is happy.

The only caveat is that you need …

I know that these little Zoho polls I'm running are totally unscientific, but they are interesting. Only thirteen people have voted on the question "Are corporate SD managers too risk averse or too eager?" but every vote has been "too risk averse."

I'm very surprised by that, because back when …

Here's a fun one to make up for all the dry process questions I've been asking: What rewards do you appreciate at software project completion? Money? Vacation? Time to learn?

(If you're reading in an aggregator, poll probably only visible if you jump to the site)

I've been pondering this series of polls I've been running and wrote the following paragraph:

Standing in opposition for this need for high productivity is risk: risk of major delay, risk of a show-stopping technical incompatibility, risk of embracing a tool or technique that is reaching the end of its …

I've been finding myself hitting the "focused test" option in my IDE and have wondered if I should feel guilty. What do you think? Here's a poll asking "How often do you run the complete test suite?"

Jeff "Coding Horror" Atwood has fingered a particular sore spot for me in Web Development as Tag Soup:

"Tag soup" is his name for the ~~spaghetti~~perfectly valid stuff that inevitably occurs in server-side, tag-based languages. A typically ~~hideous~~perfectly valid example he shows is:

 <h1>Archive for {{ year }}</h1 …

Along the lines of my recent poll on practices during project initialization, here's a poll on some common practices used during software development construction. Which of these have you found to be important for success? What have I missed?

ORA would have us believe that developer interest in the iPhone lags behind developer interest in Android or Symbian. I am skeptical

(Via O'Reilly Radar.)

What's especially amusing about recovery of Apple I's BASIC is that it was done via an MP3 file, which, as you know, is a lossy compression scheme.

(Via The Unofficial Apple Weblog (TUAW).)

I have created a short poll at Zoho on practices that can be done very early in a project's lifecycle, before a vision is really established. What do you think? What did I miss?