| My experience with Drupal is: 1) Okay, this is a decent system for people who can't code to cobble together a mostly-working prototype of the thing they need, so long as they're flexible enough to work with it. 2) Why aren't my clients flexible enough to just do things the Drupal way. 3) Why should they be? My agency sold them bespoke development, and their UX (both administration and end-user) should honestly be better than this, and adjust to their needs, not the other way. 4) Jesus Drupal makes deviating from the beaten path miserable, but it pays well and I've gotten good at it now so I guess I'll keep on truckin'. 5) Breakdown. Giving into the evidence that it seems easier to build up from a framework with nice tools and decent libraries than to chisel away at awkward building blocks, even free ones. Currently though, cleaning up messes and adding missing polish to Drupal projects created by people who are still at step 1 is continuing to be a financially responsible decision. Drupal's building blocks though, do have two important uses: They give developers who have no right to be coding a way to be productive, and the people who employ them some insurance. Brogrammer gutter rails. There are truly miserable projects that shouldn't have budgets to do bespoke development and have nothing at all unique about them, that can be built in Drupal with zero code. CRUD legos. Neither being of much interest to me anymore. |