I think drupal's take on content and defining content types and widgets to edit them is a really good take on the problem of content data.
A lot of people's jobs, as I've recently been seeing was to continuously redo what Drupal was doing out of the box. Worst of all was that they redo it inconsistently, without any rigor, and loosely.
On the other side of the coin, Drupal was not made for managing applications, it was made for creating content sites. It has very little notions of Business logic, and could feel a bit like shoehorning a car factory into a candy shop.
I think every programmer working in anything that involves a lot of CRUD should take a look at Drupal, learn how it works and try to mimic some of its ability. What do you think?
This is kind of important to me since I have never been able to get any satisfaction with this kind of problem, except briefly while I diverged a bit into a content-driven website (rather than a business driven web application) and used Drupal.
A lot of people's jobs, as I've recently been seeing was to continuously redo what Drupal was doing out of the box. Worst of all was that they redo it inconsistently, without any rigor, and loosely.
On the other side of the coin, Drupal was not made for managing applications, it was made for creating content sites. It has very little notions of Business logic, and could feel a bit like shoehorning a car factory into a candy shop.
I think every programmer working in anything that involves a lot of CRUD should take a look at Drupal, learn how it works and try to mimic some of its ability. What do you think?
This is kind of important to me since I have never been able to get any satisfaction with this kind of problem, except briefly while I diverged a bit into a content-driven website (rather than a business driven web application) and used Drupal.
