Reorganizing for Productivity

Seth Godin has a post (Reorganizing for profit) that makes an interesting point about how retailers organize merchandise in ways that seemingly work better for the retailer than they do for the customer.

When you go to Home Depot to get what you need to build something out of wood, why don't you find the glue and the wood saws and the screwdrivers and the screws all together in a section called, "working with wood"?

Source: Seth Godin: Reorganizing for profit

It reminds me of how we organize content (or scatter it, as the case may be) across MSDN and other ancillary Web sites, which seemingly works well for Microsoft than it does for most developers. For example, if you're building a Web application, how many different "aisles" of content do you need to visit before you've accumulated the knowledge you need? Is that the most productive use of your time? Shouldn't you be able to find everything related to Web development in one place?

Furthermore, as difficult as it may be to keep apprised of everything you need to know when working on a particular type of application, how do you simultaneously keep current on other application types? For example, if you've been working on a Web application for the past three months, will you be ready when your next assignment has you building an application for Windows Mobile?


Comments (1)

  1. Aaron Hallberg on Getting The Modified Files For a Team Build In Orcas. Brian Harry on Cool tool for…

Skip to main content