Today, I have a good mood, but after get off work, I see the home page of a company, so that I am uncomfortable.
The company claims to be the goal: □ Become a domestic well-known platform software supplier; □ Growth is the international leading non-programmed application software platform supplier;
Non-programming? Platform? Funny. Software development blue-collarization? Bored. The website is doing very well, but the nature of this company's boss is deceived customers, press programmers.
In http://blog.9cbs.net/hongbo781202/archive/2004/11/26/194520.aspx we discussed this problem, today I saw JBPM Tom's view:
Pitfall Many workflow management systems developers want you to believe that by using their graphical process development tools, as long as business analysts can generate process definitions. This fantasy stems from the fact that "programming is difficult". Developers' salesperson like to say "see, you don't have to write a line of code." Don't write code is a good thing, but most developers are too far from this, ignoring the mechanisms that provide a code integration into the process definition in some occasions. When the workflow system is used as an EAI platform, you must integrate code in the process. Development process definition requires business analysts and software developers. A good graphics process design tool should be able to support this cooperation.
I am also the same, um, my mood is better. :)
