One of the most common reasons new developers and perhaps existing WordPress developers resent WordPress sometimes is because of how it stores so much application configuration in the database, and most commonly, stored in different structures and in different locations.
More traditional web applications would be coded up and the database is essentially stateless. By that I mean the database only contains content, and users. It means traditionally, you could run a web app locally and on the production server, and not really have to sync the database and forth (unless there were schema updates etc).
This isn’t completely WordPress’ fault. Most developers are are comparing an application built in a framework like Laravel, to an application built on top of WordPress with a CMS included. This is an entirely different argument, one that is best left for another day.
The point remains, that if you do professional WordPress development, you’re going to have to deal with database migrations. …
Last week I flew over to New Zealand to speak at WordCamp Auckland 2014 – an event I’d been keeping my eye on for a little while.
The Auckland WordCamp was put on by the same people who run the WordPress meet up over there. I was told early on in the piece, that the group was built up of a lot more power users / users / newcomers compared to say Sydney and Melbourne where there is probably a closer ratio of WordPress developers compared to WordPress users.
It’s a pretty big trip to make to present a 30 minute talk, but I really do like Auckland – it’s one of my favourite cities, so I had no issues in making the trip across the Tasman. …
Back in February, I went to the Webstock conference, which I really enjoyed. One of the best talks was the closing keynote. The closing Keynote was by Derek Sivers and was on the meaning of life.
Now, this had nothing to do with web, or tech, or design – but still one of the best talks at a conference I’ve been able to witness. A pretty applicable subject to all, with a lot of thought provoking questions.
As of late, we’ve had a couple of large web application projects where the deliverables did not include any CMS functionality. That is, they were purely a functionality based web application.
I’ve been reflecting on both of these projects, and how we approached each one for a couple of reasons.
Firstly, did we make the right choice with the underlying framework?
Secondly, further to the first point, could we have done it faster/better/smarter if we did it another way.
Thirdly, what is our business, should we be building non WordPress projects, and if we do non WordPress, do we end up doing 100 different frameworks so-so, rather than doing one really well? …
If you want a fast and responsive website, you need to host it as close as you can to where you are.
When viewing a site, you make requests back and forth from the server, and the further away your server is (such as the USA), then the further your requests have to travel back and forth, and the slower they are.
If you have a poorly built or a WordPress site built with existing plugins and themes, there is a good chance there will be a lot of assets and therefore requests, which means, if you’re on a server on the other side of the world, it’s going to be pretty slow!
As well as offering a hosting service at Alyte for small-medium businesses & bloggers, I have used a bunch of Australian based hosts for different purposes which I’ll outline below. …