APEX

OK the title is just bait... here's my point:

I've been developing database driven software for the enterprise for almost 30 years and I've been using Apex to develop solutions for my clients that are Oracle shops since it was HTML DB. I have deployed these solutions for some big companies, including household names, all across the USA. A large percentage of these applications I would call M$ Access remediation projects, where businesses have decided to get control of end user applications and get their business data into a real database, where it can be audited and secured properly. The Access instances I have replaced with Apex fall mostly into the class of poorly designed departmental report generating utilities and data manglers. Most of them seem to have been "designed" by people with slim to no grasp on the concepts of relational databases or any kind of SQL knowledge or programming skills. This is what resulted from Access being unleashed on the world and quickly adopted by an army of semi-competent programmers and analysts. It was a smash hit because it was easy...

Isn't this exactly what is happening with Apex? Judging from the quality of questions in this forum from folks that do not seem to understand even the most basic concepts regarding relational databases, pl/sql, html, javascript, the difference between client side and server side code, I have to say I think so. While everybody has to learn somewhere, I get the feeling from this forum that there is an awful lot of really bad Apex work in production already.

I'd really be interested in the opinion of Oracle professionals on this, frankly I think I may have another career ahead of me fixing Apex deployments.

Regards,
Cranky Apex Guy.