I've been a professional C, Perl, PHP and Python developer.
I'm an ex-sysadmin from the late 20th century.
These days I do more Javascript and CSS and whatnot, and promote UX and accessibility.
I'm in a similar position. I seem to have gotten myself pidgeonholed as a Drupal developer over the last few years and D7 is fundamentally terrible. Every bad idea that went into PHP was at some point taken as inspiration for D7, from the wild naming conventions and random argument order to the way some things are randomly objects and others arrays and how nobody can tell whether something will throw an exception or a fatal error or return boolean false instead of any number of other falsy values even when you look at the documentation.
So true! Don't forget the giant and vague dblog if something does go wrong. 300 errors that the cron is trying to run while it's already running. Can you be more specific Drupal? Ha! As much as I feel your pain, I'm glad someone can relate. The salary difference between taking a step back, learning a new framework and continuing with Drupal significant, but I just feel like it will be better in the long run. Curious, what do you think about the community?
I've been a professional C, Perl, PHP and Python developer.
I'm an ex-sysadmin from the late 20th century.
These days I do more Javascript and CSS and whatnot, and promote UX and accessibility.
The community is so big it's difficult to say anything general about it - I like #drupal-support on IRC, but the contrib module community often seems to think their modules are a lot better than they actually are, and that their way of doing things is the right way... like every big project I guess.
I completely agree with that. I also think a lot of times they try to accomplish too much functionality at once rather than break it out into parts. I always look for the light weight contrib modules. Bigger module, bigger problems.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm in a similar position. I seem to have gotten myself pidgeonholed as a Drupal developer over the last few years and D7 is fundamentally terrible. Every bad idea that went into PHP was at some point taken as inspiration for D7, from the wild naming conventions and random argument order to the way some things are randomly objects and others arrays and how nobody can tell whether something will throw an exception or a fatal error or return boolean false instead of any number of other falsy values even when you look at the documentation.
I wish I was in your shoes!
So true! Don't forget the giant and vague dblog if something does go wrong. 300 errors that the cron is trying to run while it's already running. Can you be more specific Drupal? Ha! As much as I feel your pain, I'm glad someone can relate. The salary difference between taking a step back, learning a new framework and continuing with Drupal significant, but I just feel like it will be better in the long run. Curious, what do you think about the community?
The community is so big it's difficult to say anything general about it - I like #drupal-support on IRC, but the contrib module community often seems to think their modules are a lot better than they actually are, and that their way of doing things is the right way... like every big project I guess.
I completely agree with that. I also think a lot of times they try to accomplish too much functionality at once rather than break it out into parts. I always look for the light weight contrib modules. Bigger module, bigger problems.