One of the things that I dig about the software development industry (others, too, but this is where we are, right?) is that it requires some degree of constant learning.
For some, that can induce a level of fatigue. And I get it because I’ve felt it. I don’t know if it’s an age thing (I’m not old, yet, but there’s a lot to be said from going from just yourself into an apartment into a house and a family, but I digress). I think that comes with a bit of thrashing is continually trying to keep up with every new thing that comes out.
The thing is that the further I get into my career, the less I’m interested in the learning The New Thing the moment it’s released.
And I say this knowing full well it’d be easy to dismiss what I have to say since I’ve written on going deep rather than wide with technology.
But there are times where you may be interested in finding the problems in other people’s code. Perhaps it’s a dependency, perhaps it’s a third-party piece of software, or perhaps it’s a favor.
Whatever the case, if you’ve set up the project directory in a way that uses Composer to include PHP CodeSniffer and you’re using the WordPress Coding Standards, then you’re likely going to need to exclude files from PHP CodeSniffer when running the program.
Earlier this week, I was talking with a friend and fellow developer about how I handle sessions in WordPress. Specifically, we were talking about how we take PHP Sessions and WordPress and make them work together (or how we adapt the former into the latter).
This is occasionally a point of interest for WordPress developers since WordPress, as an application, is stateless.
The neat thing, though, is that it gives us a variety of ways to approach this problem. But we’re not the first (and we definitely won’t be the last) to come across this problem.
If you do any type of WordPress development for clients, then you’re likely familiar with having to work within many different environments.
Sure, the backend of each system may be very similar: That is, they are all running on some form of Linux with Apache or Nginx and MySQL. But, depending on the project that you’re working on, you may end up facing a variety of file permissions.
For example, let’s say that you’ve been hired to write a plugin or some custom functionality for someone and the work that you’re doing has to integrate with work that someone else has done. On top of that, it has to integrate with permissions on a file system that you can’t change.
Furthermore, a portion of the work you have to do must write a file to the disk. The problem? The code for saving a file isn’t working.