WP-CLI version 0.19.0 released. Tons of useful enhancements and bug fixes.
Argument Cultures and Unregulated Aggression. For open source projects, I’ve long wanted dedicated moderator resources for heated debates. A little diplomacy would go a long way.
Performance is a feature: speeding up Fusion.net. I ♥️ responsive images. Great summary from Toy and Than about the pragmatic steps we took to improve perceived performance.
Information disclosure security vulnerability debrief. The run-down on what was fixed in WP-API last Thursday. Seven hours of adrenaline.
April 2015 San Francisco Big Media WordPress Meetup. Next Tuesday at 6 pm. My presentation: “5 futures you never thought possible with WP-API.”
This is a somewhat specific detail, but it comes up a lot, so I wanted to pull it out. If you run a bunch of 5 Whys, you’ll find that a lot of times, the developer who made the first-order mistake (forgot to copy configs from QA to Prod, or deployed two apps out of order, or whatever), will say “Look, this was totally my fault, I screwed up, that’s the whole story. I’ll be more careful next time.”
The very short summary of which is: We’re going to fix this problem by being less stupid in the future.
Which, well, you can guess how that’s going to turn out.
Why do some developers at strong companies like Google consider Agile development to be nonsense? Most points resonate — particularly this one:
10. Simplicity–the art of maximizing the amount of work not done–is essential. – Most teams simply don’t spend enough time on this. A sense of urgency often overrides careful planning. The problem here is careful planning makes things get done faster. During the planning stage it feels like you’re not getting anywhere, but you are setting up for a quick sprint. This setup is often overlooked, and we end up with not only complicated software, but complicated development habits, complicated code, and generally poor software design. This slows down maintenance and new development, as we try to fit into poorly designed structures that become ingrained and impossible to improve.
How we use Github to release quality code at Fusion. Davis’ writeup is everything I’ve always wanted to communicate about my preferred feature branch workflow.