1. Open up app, start new project.
2. Enter database creation wizard, define fields.
3. Add standard DB aware stringlist or grid component. Tie properties in component to database.
4. Add DB naviation control to form. This happens to have all relevant buttons (scroll back, forward, save, delete, etc)
5. Voila, I got a working recipe program.
I would agree that this procedure is not programming. It is using a program generator. It uses no logic, design, or problem solving skills. At the end, you have a working program, but is it really the program you want? I believe that wizards often provide a good starting point, but seldom provide the right solution.
However, it think it would be folly to make statements assuming that this is how most programs are written these days. That would be akin to saying "Ford released 3 different models of SUV this year. Nobody drives motorcycles anymore." There is no logical connection between the fact that wizards exist and that some people use them and your assumption that nobody programs anymore.
And what kind of experience do you have to be able to make such a statement about my opinion? I see where your posts lie on this board, and that really tells me much. Tell me this though: What difference is there in slapping a few components (controls) onto a form and a few rudimentary statements, and doing something like prepare a Powerpoint presentation or an Excel spreadsheet or even a Word doc? Personally I find no difference whatsoever, having done all of them (VB, Delphi, and Oracle forms if you want to know that side of my experience).
While I'm not overly familiar with AlexCuse's posts on this board lie, I've read many of his posts on other boards, and they've told me much as well. Things such as he is intelligent, considerate, clever, and at times funny.
As far as "slapping a few components on a form and adding a few rudimentary statements", if that's what your programs look like, then I would agree that you're not programming. However, I slap controls on forms, remove much of the time and effort involved in creating a user interface, and focus my time and energy on the complex problems that go on behind the scenes are are typically not visible or appreciated by the end-user. I also know that there are many others that behave similarly. I feel that we are "programming" by any definition of the term that has any merit.
Just because problems can be solved in a more hands-on, detailed manner doesn't make that a good solution. Use C (not Visual C or anything like that, but old school C) to create a windows program and you are likely to spend half of your time on the user interface. The fact that this has been greatly simplified is, in my not-so-humble-at-the-moment opinion, the best thing since soda in a can (sorry, I don't drink much beer).
The more tools that are developed that allow us not to worry about certain parts of our applications, the more time we can spend on the complex or groundbreaking aspects. Thus, innovation is born.
When you want a hamburger, do you :
A) plant some wheat, which you will later turn into flour, which you will in turn bake into a bun
B) plant tomatoes, lettuce, onions, mustard seed, etc. to create your condiments
C) buy a cow, slaughter it, trim off the meat you want, and cook it
or
A) Buy a hamburger.
If you spend all of your time raising livestock and crops for your burger, how will you ever find time to program?