[flexcoders] Re: Brocade Case Study

2005-11-07 Thread michael457728
Dave Thanks for your reply, I like your front to back approach as it enables you to go out and generate customer awarness whilst the product is still in development. It sounds like you are alone in your front to back design, what are the objections to it? Mike --- In

[flexcoders] Re: Brocade Case Study

2005-11-07 Thread Dave Wolf
Ya know, its funny. As developers this isnt a value you think of first hand, but I have to saw clients love that they get a demonstrable product very early in the development cycle. Now they are out there generating leads and revenue before the offering is even complete. There are others who

RE: [flexcoders] Re: Brocade Case Study

2005-11-07 Thread Tim Beynart
37 Signals is great for UI, no doubt, but those boys seem to have a serious antiFlash angle on web applications. -Original Message- ... So yes this is not a common approach but you will find other thought leaders such as 37 signals (probobly one of the best user experience groups

[flexcoders] Re: Brocade Case Study

2005-11-07 Thread Dave Wolf
Yup, no doubts. Not everyone can be totally enlightened smile. He just wanted to know if other folks ever approached development using a front-to-back style other then us and was it common. No one likes to feel like they are too much off on a flyer. I can dig that. The net-net though is

[flexcoders] Re: Brocade Case Study

2005-11-06 Thread Dave Wolf
It can be difficult because the devil is often in the details. What we do with our clients is what we refer to as a Model Design. In the MD we develop the entire user interface, bind to static data, include a functional spec, data model, test plan and a project plan. Its the project plan you