I often brag about the fact that I’ve dumped heavy tools like XAMPP in favor of Vagrant. I’m quite proud of this accomplishment, and I urge every other developer I meet to look into Vagrant.
My ideal blogging app/content management system/application platform would take the entire stack into account.
Determining which methods in your application needed testing used to be easy – test everything exposed by the public API. But once you invite other developers to contribute, you are exposing a whole other set of internal APIs to the team. The behavioral consistency of these methods is just as important as that of the public API, so shouldn’t you be testing them too? I would argue you should, even if this internal API consists of private and protected methods. To make life easier, I’ll give you a couple of tools for testing these limited-visibility functions without forcing everything to be declared “public.”
I use both Mac and Windows for development because I’ve managed to set up a Linux-style command environment on both. Here are some simple steps you too can follow to have the power of Linux-style commands right from the Windows command prompt.
Back in 2011, I was talking at WordCamp Portland with a few people about how we could use WordPress to replace our presentations. Fast forward to 2013, and I get to make that dream a reality. We just launched seoslides, and it’s already making a huge impact on my content!
Last weekend, Matt Mullenweg spoke at length about what the future holds for WordPress development. I took some time to share a brief proposal for one change that could be made farther down the road. Today I’d like to share another – more in line with Matt’s proposal that future WordPress development be focused around […]