Everyday I spend time working on products for our great clients, I specifically spend a great deal of it writing code and building features. But I’m not just creating new features, I’m also creating new opportunities…opportunities to break that product. Here are the questions developers need to ask before turning in their tasks, and how they’re going to help you code smarter.
This is probably the most non-technical post I’ve ever written about coding or WordPress ever. In fact, it’s not about WordPress or coding at all. This post is about how philosophy and our personal beliefs, things that are extremely personal, that end up helping us at work. I’ve been a Stoic for a few years and ever since I read The Obstacle is the Way, Stoicism has done more than just help me personally–it has helped me professionally. I wanted to take a moment to explore some ways Stoic practices have informed my dev work.
Please note that this post isn’t meant to be evangelical; take what works for you, what resonates with you, and leave out what doesn’t.
These are some tenets that have helped me be a better developer (and all around better person!):
On a recent project, I started to feel a bit overwhelmed with managing numerous layers with z-index. The thing about z-index is that all of the layers have to be in order, so I end up with multiple z-index declarations in multiple files all over the place. It’s also hard to keep track of the numbers; bump one up and you have to go bump all the others up as well. It gets a bit tedious, especially when you have numerous layers. This can all be fixed with a little bit of Sass, and here’s how to do it!
So, you get an email like this one every time WordPress publishes a new release. 4.2 just went out, so I got this email a few days ago. I’m not a serious plugin developer like most out there. They aren’t premium plugins; I just share my code because it’s helpful and it’s nice to know people use my stuff to help them do things. So, usually, I update my plugins after the release. Serious plugin developers are going to test their plugin before the release. For this tutorial, we’ll be updating it post release.
It’s good to let users know what version your plugin works on. When I looked at this list, I thought a lot of these plugins should work in 4.2, but people are probably not trying them because they are so outdated. This is not uncommon, especially if you’re just starting out or have that usual nine-to-five. I just got this email, so it totally sparked this post! Let’s get these updated!
In this tutorial you will learn how to:
- Use WordPress on Git to easily switch back and forth between versions for testing
- Update your plugin’s ‘Tested up to’
- Publish your changes to WordPress.org quickly