Funny programming-free

I am in a good mood to go to work today, but after work, I am uncomfortable to see the homepage content of a new company. The company's declared goals are as follows:

□Become a well-known platform software vendor in China;
□Grow into an international leading supplier of NLE application software platforms;
□Become a pioneer in blue-collar software development; non-programming? Platform? Funny.
Blue-collar software development? Bored.
The website is doing quite well, but the nature of the bosses of such companies is to cheat customers and squeeze ProgramMember.
After reading this question, I saw the idea of Tom in jbpm: pitfall)
Developers of many workflow management systems want to convince you that by using their graphical process development tools,
Business analysts can generate process definitions. This fantasy stems from the fact that "programming is difficult.
Sales staff of developers like to say, "Look, you don't have to write a line. Code". It is a good thing that you do not need to write code,
However, most developers are too far away at this point, ignoring the fact that, in some cases, they provide a way to integrate code into the process definition.
The mechanism is very suitable. When using a workflow system as an EAI platform, you must integrate the code in the process.
The development process definition requires the cooperation of business analysts and software developers.
A good graphic process design tool should be able to support such cooperation. So is my opinion. Well, I feel better.