Writings on building software delivery capabilities, delivering digital & technology, and running live services for ambitious organisations.
React is improving the way we build frontends, but I find common patterns are making our apps more complex to write and manage, and more difficult to understand.
A couple of months ago I gave a talk about PostgreSQL, and specifically using the Array datatype, at London Ruby User Group and I wanted to take some time to dive into this in more detail.
So you are trying to build a fast moving digital organisation, one that responds to market opportunities, is decisive and can get things delivered. One of the challenges you may encounter is a thing we call Analysis Paralysis.
Intersectionality, BAME, cis, anonymous hiring, inclusion. These words are likely not on your ticket if you are playing privilege bingo. Like a canary in a coal mine, a lack of understanding of these concepts will likely mean your daily actions reinforce systemic discrimination.
There have been a few rumblings recently between the subculture of TDD-lovers and the rest of the programming community, as always. I’ve heard reports that TDD doesn’t work, that it is snake oil, and that there are studies to suggest that TLD and TDD are no better than each other in a scientific study.
The primary goal of slicing software is to make it cheap to ship, and inexpensive to ship additional features.
With the latest reforms to IR35 having come into effect on April 6th, public sector bodies (PSBs) are facing the mounting challenge of keeping teams filled. This, coupled with the Civil Service-wide recruitment freeze introduced in 2010, is a particular problem for PSBs tasked with delivering digital projects, where software engineering teams were once largely made up of contractors who now have an incentive to look elsewhere for work. The reforms are here to stay, so what options do PSBs have in terms of continuing to deliver good digital products?
We live in a world increasingly intertwined with software; the Internet of Things allows companies to collect data relating to not only what we type, but on where we are, who we are with, how we drive our vehicles, and more intimate details like our sleeping patterns and heart rates. In the near future it will be trivial to sequence an individual’s genomic information and make predictions about their personality traits and health.
From keeping in touch with friends, to hailing a cab, and even allowing us to control the temperature of our houses from our phones, Technology has become increasingly pervasive, changing the way we do things and how we interact with one another. Contrary to what some would think, Education was not left out of this revolution. In recent years, an incredible number of digital tools and platforms have seen the light of day which try to improve how people learn, how teachers share their knowledge and allowing pedagogical resource providers to reach an ever increasing number of people. But in Education, things cannot change as rapidly as in other sectors because the cost of doing something wrong has long lasting consequences. Pedagogical practices have been refined over the years and introducing changes requires a lot of thought.
For the last year or so, the majority of our new projects at Made Tech have used Ansible as our go-to tool for provisioning and configuring our servers with the software that runs on them. We’ve paired Terraform with Ansible and Chef previously for creating our cloud resources, but have recently been experimenting with using Ansible to see if the one tool was capable of both of these stages in our infrastructure setups. We’ve not been disappointed with our experiences so far.