I get your point about good code vs. bad code, but in my experience that doesn’t have much to do with legacy vs. modern frameworks. It has to do with the skills and aesthetics of the original developer. I work on framework-based code (Laravel, etc.) that I don’t find very enjoyable, and I work on procedural PHP from ten years ago that I find easy to work on.
Programmers who focus on their own enjoyment or priorities like working with the most recent tools and frameworks will turn up their nose at less appealing legacy work, and that’s why there’s so many companies unable to hire people to work on their business systems and web sites. To some developers an older code base is just a turd, to others it’s an opportunity. After working with a legacy system for a while and incrementally refactoring it, if my client decides to rewrite it they will talk to me rather than sending out RFPs. I have two ground-up rewrites in progress right now that started as legacy support work. Those clients didn’t write RFPs or ask anyone else to bid on the work.
I agree that learning Wordpress, or anything, takes time. Wordpress certainly has some bad design decisions (mainly caused by maintaining compatibility with a huge installed base), and some ugliness to work around, but on the other hand WP has a large and mature developer community, good documentation, and lots of tools and add-ons.
from Hacker News - New Comments: "WordPress" http://bit.ly/2Sta6ti
via IFTTT
No comments:
Post a Comment