These distinctions are hard. For the vast majority of clients, if you are writing CSS, you are probably also writing HTML. If you are writing HTML, you are probably querying the DB or a remote API in order to generate that HTML. If you are querying a DB, you might be designing a schema. If you are calling an API, you might be managing the local server cache. Therefore there is no distinction between back/front end developers that clients will ever care about or be able to request accurately.

In my opinion, we’re all “templaters”. As a templater, I need a sys-admin to give me an environment in which to work and a designer to tell me how it should look. I’ll take it from there, everything from generating to styling the content.

I’m working on a GoDaddy plugin at the moment, to allow the wp-admin user to purchase domains through the GoDaddy API. This is a crucial step in a larger project to allow non-technical clients to manage their own launch process. Turns out, GoDaddy’s API is weird.

I’ve got a custom class, `WP_Multi_Error`, that extends `WP_Error`. You can pass it an array with any number of members, of any type. It loops through them and, for any that are error objects, it merges them together into one error.