I’m currently working on a project that I inherited from a previous team in which I’m working on improving the code quality. The details aren’t terribly important, but here’s what you need to know to have enough context for this post:
- I didn’t design the application, but the client wants to keep the existing design and feature set
- The budget only allows for improvements agreed upon during the planning phase – nothing more
- The initial codebase was developed by someone else that opted to do things in a less elegant way
As far as the last point is concerned, “less elegant” could be chalked up to laziness, or it could be chalked up to ignorance.
When possible, I try to believe the best rather than assume the worst, so I’ve opted to go with the fact that the team was under a deadline to ship rather than to build an elegant solution.
That said, I think that all developers have found themselves in this position: We’ve inherited – or contributed – to some codebase, looked around, and said:
I wouldn’t have done it that way.
Often times, the implication is that our way is a better way than the way it’s currently done. In some cases, that’s right, but if developers often think this and another developer wrote said code, where does that lead?
Anyway, this is not the first time I’ve found myself in this position, and it certainly won’t be the last, but it seemed like something worth discussing if for no other reason to share my thoughts on it.
Continue reading “Three Thoughts on Improving Code Quality in Existing Projects”
In my experience, one of the toughest concepts for new WordPress developers to grasp is the difference in actions and filters.
By this, I don’t mean that they are difficult to use. In fact, I think most developers have a pretty easy time picking up how to hook their functions into hooks and filters when needed, but it seems as if its a bit challenging to grasp WordPress page life cycle and how actions and filters fit into the overall context of WordPress.
So in my latest article at Envato, I try to provide a clear understanding of WordPress Actions and Filters.
Continue reading “Understanding WordPress Actions and Filters”
This particular aspect of development is one that I’m still experimenting with; however, there are certain aspects of it that have remained constant.
To follow up with yesterday’s post, I thought I’d share several things that I’ve consistently done that have improved development as well as some of the things that I’m currently doing that are proving to be useful.
Though I manage them similarly, I think that each type of file is deserving of its own post, so I wanted to start by sharing how I’ve been using LESS in WordPress.
Continue reading “My Strategy For Using LESS in WordPress”
Recently, fellow tweep @Krogsgard asked about some of the things that I do to go above and beyond the basic set of WordPress Coding Standards.
To be clear, I think that the Coding Standards are the foundation on which you need to be building your coding style. They’re the foundation of writing professional-grade code for WordPress, so start with that and build on top of it.
Everything else is just bonus.
So, with that said, here’s what I try to do to go above and beyond the WordPress Coding Standards.
Continue reading “Going Above and Beyond The WordPress Coding Standards”