I love the idea of outsourcing to rural parts of the country because a) I like keeping jobs in the US if possible (although I’m not a protectionist by any stretch of the imagination), b) it gives the under-employed more choices and c) it’s another step toward my dream employment environment.
I see a future where people are listed like books on Amazon with ratings, reviews, descriptions (aka resumes), prices and availability, to be placed into a shopping cart to form ad hoc project teams based on the needs of the project and not on the locale of the participant or something as restrictive as “employer.” I admit that I this article is only a small step and may not even be in the direction I’m hoping for, but as I’d like to live in a rural area (central Oregon) and still get to do interesting work at reasonable pay, I’m more than happy to read into things.
I've been reading each of the Software Factories articles with great interest. Part 1 and part 2 did a particularly good job describing the elements of the problem space, I thought. However, when I get to part 3, I was ready to see a solution. Instead what I got was a long abstract piece defining the bits of what makes up a software factory. This is the kind of thing I'd be ready to read after I was shown a concrete example or two of working, running software factories. Do other people like reading these long, abstract articles? I find them tedious unless they're filling in and generalizing the details of something that I've already got a handle on.
