Airbrake: The error app. Track errors seen by your users.
Tag Archives: web development
Software Effort Estimation Considered Harmful. Oh I’ve run into this so many times.
How we build stuff at Grist. Written for an internal audience but interesting nevertheless. I’m surprised they get that much mileage out of Pivotal Tracker.
How We Build CMS-Free Websites. The ultimate mid-life developer crisis in which they essentially reinvent the CMS with Github.
PHPUnit is a go
Many thanks to Zack for the Dev Day presentation. I’m somewhat ashamed to admit it’s my first formal(-ish) introduction to unit tests, and now I’m pretty excited about what they can offer the WordPress project. Check out the Trac to get started. Rewrite API tests coming right up…
#wcsf: The Zen of WP Development
The Zen of WP Development is being one with the code, and creating compelling web experiences with proper uses of the core API. It involves: Focusing on the question at hand, and ignoring distractions. Distilling complex situations into simpler parts. Pulling from deep knowledge of… Continue reading →
Software Inventory
The bug database is obviously a great thing to have. Bug reports should be complete, accurate, and actionable. But I have noticed that in many real-world companies, the desire never to miss any bug report leads to bug bankrupcy, where you wake up one day… Continue reading →
#nyc12: Hacking WordPress in the Newsroom
This morning, I gave the second of three CMA NYC sessions I’m leading this week: You publish with WordPress, are comfortable with editing theme templates and making basic CSS changes, and you’re ready to take your site to the next level. Join Daniel Bachhuber, code… Continue reading →
#wcphx: Five tenets to mastering WordPress development
Enlightenment is knowing what your code is doing and why. Thankfully, instead of having to depend on your inner calm, there are a number of tools and strategies you can use to better see what’s going on. We’ll survey a range of topics you should… Continue reading →
Thanks to a bunch of hard work by Thorsten and others, the open source CLI scripts we have for exporting and importing WordPress sites are getting better and better.
When exporting, the script gives you a summary of what will be included in your export file.
For importing, it would be nice if the script pre-flighted your data and told you how many total posts were to be imported, whether new tags were going to be created, identified the custom post types in your export file that were to be rejected by the site, etc.
Also, we should figure out a better way to make sure all of our internal scripts are regularly open sourced (and synced to most recent versions).