Inheriting WordPress Projects: Tips For Development


If you’re running a business that focuses both on developing solutions from the ground-up or that focuses on implementing a custom solution in the context of pre-existing projects (or maybe both), then you’ve likely – at some point – been in the situation of inheriting WordPress projects. Tackling projects from either handle brings its set of challenges – most of them welcome – but it seems to be far more common place for people to complain about working with a pre-existing codebase.
It’s not that I don’t get that feeling, but I do think there’s a level of immaturity in doing that. On the one hand, yes some codebases are outright terrible. But then some codebases aren’t that bad. In fact, I’d argue they are just a little bit different from how you’d develop it.
This is a case in which standards come into play, but I digress on this for now.
So let’s say you’re inheriting WordPress projects and you’re not particularly stoked about the codebase with which you’re working. How is it that you can still enjoy the work that you’re doing without feeling like you need to critique every aspect
Source: https://managewp.org/articles/14727/inheriting-wordpress-projects-tips-for-development


Source: https://williechiu40.wordpress.com/2017/03/29/inheriting-wordpress-projects-tips-for-development/

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s