Software Development insights, articles and news

A Minimum Deliverable Value (MDV) is a lightweight, functional outcome that tests a core assumption or delivers operational insight without the bloat of a full MVP. This is ideal for validating a specific assumption, exploring a technical opportunity, or demonstrating early value before investing in a larger, traditional MVP or product build.

At a recent Sheffield AI meetup, I gave a talk that aimed to unpack a big question: Is AI coming for your job? Short answer? No. But not for the reasons you might think. Rather than fall into the trap of hyperbole, I approached the topic by stepping back and asking a different question: How have the skills and resources around building software changed over time?

Modern cloud environments provide several different mechanisms and services for deploying a web application. In a more traditional scenario, an application may be deployed to a bare metal server or a virtual machine (VM).

At The Curve we do a lot of talking about “The Internet of Things”, we offer IoT consultancy services, we even host IoT events, and at the office, there’s more often than not, a half-assembled “thing” sitting on a desk waiting for its life as a connected internet device to begin.

We’re often engaged by our clients to develop Minimum Viable Products (MVPs) of a given product or system. More often than not we see a common and recurring problem with the original brief – the “MVP” is packed full of features of varying shapes and sizes.

As a recently appointed Freeman at the Company of Cutlers in Hallamshire, The Curve were given the opportunity to attend their regular monthly Tuesday Breakfast members event, and present a topic which gives rise to some of the most pressing challenges and opportunities facing companies today.

Story points estimation is an estimation method that is often used in agile software development. Story points are a unit of measure used in agile project management to estimate and compare the complexity, effort, and relative size of features or user stories within a project.

Sometimes it can be useful to request a manual approval before a deploy is unleashed on production. GitHub supports manual approval when you use environments, but only on public repositories or private repositories for GitHub Enterprise. In this post, I look at how GitHub Actions and Microsoft Teams can be used to create a manual approval process.

We use continuous integration and continuous deployment techniques regularly in the delivery of our projects. Whilst our team predominantly uses GitHub Actions these days, we’ve supported a variety of CI tooling including Jenkins and GitLab Pipelines.

Estimating the effort involved in any project can be a challenge, and software projects are no different. Arriving at an accurate estimate and plan is tricky, to get right.

In this post we take a quick look at the gadgets featured during The Curve’s demo at our first in-person event that we hosted the other week as well as a few of the considerations that went into the design, build and software.

What is the HubSpot API? HubSpot provides a standard REST API as well as webhooks. The webhooks allow the custom integration to be notified of changes from HubSpot efficiently without the need for polling the API, whilst the API allows the integration to create, read and modify the data in HubSpot.

September was a busy month for us at The Curve, but Paul and I were able to get some time out of the office to attend The Things Conference in Amsterdam.

At The Curve, we build products for our clients. These could be business systems that are used by internal stakeholders that we develop using a product mindset, or B2C products our clients then use with their own customers.

On the 19th July 2024, the world witnessed what could easily be described as the largest global outage IT outage in history when CrowdStrike, a cyber security solutions provider, shipped a defective security update that impacted an estimated 8.5 million Windows computers worldwide.

The Internet of Things (IoT) refers to a network of devices or objects that contain or are made up of a variety of sensors and other data gathering technologies that can connect and share information with one another as well as sharing data with other devices through an internet connection.

Advances in IoT (The Internet of Things) technology has revolutionised the way devices interact with each other and with us. From smart homes to industrial automation, IoT devices rely on continuous, real-time communication to operate efficiently and effectively.

As the Internet of Things (IoT) continues to expand, the need for efficient, reliable, and scalable communication protocols becomes increasingly crucial. WebSockets have been a popular choice for real-time communication between devices and servers, but a new contender, WebTransport, is emerging as a powerful alternative. This blog post delves into what WebTransport is, how it works, and why it represents a significant improvement over WebSockets, especially in the context of IoT.

AWS Lambda and Azure Functions are popular Function-as-a-Service (FaaS) offerings and are a staple of the serverless landscape. With FaaS offerings the cloud provider is responsible for running and managing the underlying compute that powers the service.

In this article we look at compiling applications for different CPU architectures using Docker to emulate on an x86 host, with a working example of packaging libcamera-apps for Alpine Linux for an armv7 device (a Raspberry Pi Zero) and armv8 (Raspberry Pi Zero 2).

Agile has been a popular software development methodology since the early 2000s. Despite being around for over two decades, agile can still be misunderstood or incorrectly applied.

Understanding OPELThe National Health Service (NHS) in the United Kingdom uses the Operational Pressures Escalation Levels (OPEL) system to monitor and manage the pressure on its services.

In the quest to promote a culture and ethos of excellence and quality within the dev team at The Curve, it goes without saying that we should have a set of coding standards and best practices under which we operate. Not process for process sake, but a set of guidelines where everyone knows the expected standards to build well-coded software.