What this technology blog is for
This is a technology blog about the work rather than the pitch. Every article covers something we deal with regularly: why a website is slow, whether to build software or buy it, which barcode symbology survives a cold store, what a maintenance plan should actually include.
The writing avoids two things. It does not invent statistics, and it does not pretend every answer is to hire someone. Several articles here recommend the cheaper route, or no route at all, because that is often the honest answer.
What you will find here
Five areas group the articles, matching how we work.
Web design and development covers building, rebuilding and speeding up business websites.
Enterprise software covers custom applications, automation and integration between systems.
Hardware and devices covers barcode and RFID, point of sale, printing and asset tracking.
IT support and maintenance covers keeping all of it running.
Industry notes covers the constraints particular sectors bring.
New articles publish twice a week, on Tuesday and Thursday morning.
Where to start
If you are weighing up a project, the pieces on
build or buy and
briefing a website project are the most useful first reads. Where something is already broken, start with
why your website is slow or
investigating intermittent faults.
If you would rather just ask, our
contact page goes straight to the people who do the work.
Who writes it
The team that does the work writes everything here. No content agency, no keyword brief. That shows up in the detail: the article on POS integrations talks about month-end reconciliation because that is when the calls come in, and the one on rugged devices talks about glove operation because that is what decides a deployment.
Where an article makes a claim about performance or cost, it says how we arrived at the number, or it says plainly that the figure varies. There are no case studies here with invented percentages attached to them.
Using any of this
You are welcome to apply anything in this technology blog yourself. We write most articles so a competent person inside your own organisation can act on them without hiring anybody, and several say outright when that is the sensible course.
If you would rather have it looked at properly, the four service lines are
business websites,
enterprise solutions,
hardware solutions and
technical support.
How to use this blog
You do not have to read it in order. So here is a quicker route.
If something is broken now, start with the support and maintenance pieces. They are written as procedures. Because of that, you can follow them without background reading.
If you are planning work, start with the decision articles instead. Build or buy. Redesign or rebuild. WooCommerce or Shopify. Each one sets out the trade-off plainly.
Meanwhile, if you just want to know how we think, pick any article at random. Above all, we try to say what we would actually do, including when that is nothing.
