Sam says you should read this
This blog was created with the BlogFile software, written by Samuel Levy.

You can find Sam on Google + and LinkedIn.
 

The Editor With No Name - an informal case study into what went wrong with Gutenberg

So WordPress 5.0 has been released. It happened just in time for WordCamp US, conveniently enough, and now "Gutenberg" is just referred to as "The Editor". Of course the "Classic Editor" (which was actually TinyMCE all along) has been given a more recognisable name reminiscent of "Classic Coke", but stock WordPress 5.0 includes the editor formerly known as "Gutenberg" by default.

This has made a lot of people very angry and been widely regarded as a bad move.

But why is the community so angry? Essentially this comes down to one thing - Gutenberg is a prime example of how not to bring a new prod…

Four development methods you didn't know you were using!

Waterfall is hard, and agile is confusing, so why should you put your team through them? Instead, you are probably already using some of these alternative development techniques! You won't learn about these in a text book, but you'll find them in use all over the software industry. Let's learn about how we manage small teams:

1. Whack-a-mole development

This is the most common development methodology around. Almost all small teams do this to begin with, and businesses can grow huge off the back of Whack-a-mole development. So what is it?

Whack-a-mole development is a process where your developer…

The Guten, the Berg, and the Ugly

Or: How I learned to stop worrying, and love like accept Gutenberg.

For those not in the loop, Gutenberg is the controversial new editor for WordPress. Despite not using WordPress on this blog, for reasons poorly explained elsewhere, I do use WordPress for client work. With Gutenberg becoming the default editor in the fast-approaching version 5.0 of WordPress, I figured that I should install the plugin version, and at least try to understand what it's all about.

Why a new editor?

Because the old editor is crap.

Ok, now that I've offended everyone, it's not crap, but it's also not sufficient for b…

The small tips about freelancing that I've learned over the years.

This was originally a post on /r/freelance over on reddit, but I'm re-posting here for posterity.

I've been at this for a fair while, and this is some of the wisdom that I've been told or learned, often the hard way.

The typical full-time employee costs a company 2-3 times their nominal salary

Use this as a basis for deciding your rate. $90/hr might sound like an expensive replacement for an employee getting paid $30/hr, but that $90 is the total cost, and stops immediately when the project ends.

A client asking for 6+ hours in a day will cost you 8 hours

You will achieve nothing useful (read: bil…

Workflows for a small team of gits

In my current role at cpap.com, I'm working on improving the workflow of our small development team. We made the switch from SVN to git a couple of years ago, but the tools we had available at the time didn't really support us well, so we had to fight to stop using git like we used SVN.

As the developers got more comfortable with git (and as we brought in new blood to the company), the workflow has organically changed to be closer to the original plan. Now only the lead developers push changes into master, and developers pull off feature branches when they get a new ticket.

It's working well, b…