And that is why the business side says we are not doing our job. Let me show you an example and I haven't looked at this since 2002 so bear with me.
1. Design = Math (excel spreadsheets) + artwork (apples and jpgs) 2. Engineering = Hardware (autocade) + Electrical (autocad) + Software (C) 3. SQA (testing of all steps) 4. Compliance (making sure the I's are dotted and the t's are crossed) These 4 steps are the natural progression for building slot machines in vegas, at least for the R&D portion and then you need to factor in manufacturing and support Each step is followed by the next step, in other words, math and artwork have to be done before moving on to engineering and so forth. Any one of these steps that are circumvented will destroy years worth of work. Its like the old saying of plan your work and work your plan and the lack of that is why the software business has such a bad name in the areas that matter, which are the business. Yeah I know, you guys are the keepers of the gate which means you tell the business what they can and cannot do. For myself, as the business side begins to realize that they can actually develop the process (not the software), more and more software guys will be put out of work because they are not willing to do the essentials which is to make the business process flow seamlessly from stage to stage. Yep, I know I'm in the minority right now, but those that are wise and have worked at the enterprise level (not the dept level) will agree with me because they too have seen what is happening. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Stephen Russell Sent: Saturday, February 13, 2010 9:43 PM To: ProFox Email List Subject: Re: .NET and other languages for a VFP developer On Sat, Feb 13, 2010 at 2:55 PM, Virgil Bierschwale <[email protected]> wrote: > Agreed.. > > But I'm saying that we need to do better by implementing a blueprint > type system where all of our work is properly done at all steps of the > process just like what already exists for the building process because > if we don't, we will never be able to achieve what we should be able to achieve. ------------------------------ I have to disagree with you here. You don't need a blueprint. You just know what they want the room to be for and you figure out the rest. That is what the pro of today does all the time. PHBs are rarely the problem. -- Stephen Russell Sr. Production Systems Programmer CIMSgts 901.246-0159 cell [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/5d399b3abe6641cf93aca27e99af3...@bierschwc0bba6 ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
