On Oct 9, 2007, at 3:49 PM, Shaun Bergmann wrote: > > On 10/9/07, Will Parker <[EMAIL PROTECTED]> wrote: > > The bottom line here is that the hiring manager wants to get this > done with _one employee_, instead of the IxD, software dev, and > software-developer-in-test that the job description really calls > for. He might find that individual, but he's not going to get more > than one project shoved through his underpaid star player at a > time, whether he tries to or not. > > Exactly. Thankfully for Vince, he's working for a company that has > a fairly flush compensation plan for the emotional / > psychological / mental / physical burnout he's in the fast lane for.
Oh, so you actually _believe_ HR when they hand you the benefits packet? Interesting. By any chance would you like own part of the Golden Gate bridge? > I wasn't speaking to this exact job posting as much as I was > responding to the resulting sideline conversation about the 'rule' > that "Programmers" are inherently and always bad Designers. ... > Sure, it's rare, but it's not the black and white rule that it's > often portrayed to be. Absolutely. The problem is that the two roles, in order to be performed _well_, require a great deal of attention to very different sets of problems, and the process of paying that attention requires more time in a day than one person can reasonably work. Throwing more people at a problem doesn't necessarily speed up the process, but throwing *enough* people at the problem is arguably a key requirement for products with a fixed release date. -Will Will Parker [EMAIL PROTECTED] ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://gamma.ixda.org/unsubscribe List Guidelines ............ http://gamma.ixda.org/guidelines List Help .................. http://gamma.ixda.org/help
