
Originally Posted by
TheAnimus
Not so much the 'deployment platform' (because i'm not going to get into a debate of open-friendlyness of java applets vrs flash vrs silverlight, regretabbly my narrow minded view is, sod that <10%, and at work i'd get laughed out of the trading floor for suggesting a switch from windows) but the way design and development teams interact. The platform is a bugger to change, but the development toolset can always be agumented.
Right now, i'm having fun with analysists. I've completed about 14 projects which are more complex than this one, which has now managed to clock up 4 weeks of my time, and about £8k of my resources, in less than a week. It is soley because you've got someone who is demonstraiting they don't know which side of the fence to be on, and rather than helping us, its a major hinderance.
I like the idea of really bringing together the designers + the developers, so both can truely specialise where they belong, where they function best. This will lead to faster developement of a higher quality. WPF i've not really fully embraced, but i do detest GUI work, i much prefer having some modeller give me some maths, me look at it with a trader and decide what approximations he will find acceptable, then i run off and figure out how will will do a few million of them a snap, vrs the cost of the hardware and stability issues. The notion of having a GUI designer be able to bolt straight onto my view, is wounderful, as the main reason I don't have one at present is that they wouldn't offer enough of a cost saving in my time. Its all round a good think, it would create a GUI designer job, who would free up my time for more profitable work, whilst making the users who ultimately decide if i get a new kitchen this year, like the software more.
Now if only the uni's weren't offering bull***t training courses which sound all web 2.0, and often mean students can only just work a graphics package, i'd be able to ask for a nice cheap graduate slave to do my GUI work. Oh well, mabye soon.