With so many options available, how does one choose what to use for a new project? If the project is a website, the question of whether or not a CMS is appropriate is one of my first considerations. But sometimes it’s hard to tell where a website ends and a web application begins.
Log files are just good practice; not only can they help in development and debugging, but they can act as silent sentinels, watching over your code and helping you find a quick solutions when things go wrong.
Have you ever written plugin code in WordPress that was dependent on another plugin to run? If your code tries to execute before the plugin you require has loaded, obviously, it won’t work. There’s a very simple way to make sure that your plugin doesn’t run until it’s ready.
Development tools like Angular.js, React.js, and Vue.js have transformed front-end website/web application development. It’s actually possible to write whole applications in JavaScript now in a cohesive, management manner. The real question is: should you? The answer is, of course: it depends.
As a developer, you’ve no doubt been asked “can you do [insert user request here]” more times than you can count. The answer is pretty much always “yes.” The tougher question these days is “how” … there are hundreds of ways to get things done these days. In this post, I’d like to share some of the things that shape my decisions about the “how.”
In a previous post, I introduced Wordpress Plugin Boilerplate (hereafter referred to as WPBB for brevity), an attempt at standardization for the way Wordpress plugins are developed.
