{"canonical_url":"https://engineer.company/glossary/software/","content_markdown":"# Software\n\n## What it is\n\nSoftware is every part of a computer system that can be changed by writing instead of by\nsoldering: the programs, the data they carry, and the settings that tell them how to behave. The\nword is a mass noun in English, so a single item is \"a piece of software\" or \"a program\", and\nsomething a person opens to do a job is usually called an application. \"Code\" tends to mean the\nsource a developer edits, and specifications sometimes abbreviate the whole thing to SW.\n\nIts usual opposite is hardware, the physical machine, with firmware in the gap between them. The\nNIST glossary draws that line through change: software is \"computer programs and associated data\nthat may be dynamically written or modified during execution\", while firmware is the kind that\ncannot be modified while it runs. A laptop's operating system is software; the code in its\nkeyboard controller is firmware; the keyboard is hardware.\n\nInside software there are layers. System software, such as an operating system or a device driver,\nmanages the machine. Application software does something for a person: a spreadsheet, a booking\nsite, a messaging client. Between the two sit libraries and packages, ready-made pieces that both\nkinds are assembled from, and in practice most of the code in a modern product arrived that way\nrather than being written for it.\n\nOne more distinction decides a lot later on. Source code is what people write and read; a compiler\nor an interpreter turns it into instructions a processor executes. Both are software, but they are\nnot interchangeable when you buy it. A delivery of compiled files alone is something only its\nsupplier can change.\n\n## Why it matters\n\nAnyone commissioning, buying or renting software is choosing who carries its upkeep. The thing that\nmakes software attractive, that copying it costs nothing and changing it after delivery is cheap\nnext to changing a machine, is also why it is never finished. The components it was built from\npublish fixes. Operating systems and browsers retire interfaces. A flaw is disclosed in a library\nnobody on the team remembers choosing. Each of those turns into work for whoever owns the code.\n\nThe common routes divide that work differently:\n\n- **Rented as a service.** The vendor runs the updates and the servers. You inherit their release\n  schedule, their pricing and the effort of leaving, and your data lives on their side.\n- **Licensed and run yourself.** You choose when to upgrade, and you also do the upgrading, the\n  backups and the security patches.\n- **Built for you.** It fits the process instead of the other way round, and its maintenance budget\n  is yours for as long as it runs. The cost that decides whether that was wise comes after launch.\n- **Open source.** Under a licence that meets the Open Source Definition you may use, study, change\n  and redistribute it. Somebody still has to apply the updates; free to obtain is a different\n  property from free to operate.\n\nWhichever route you take, two questions about the result are worth asking before signing. What do\nyou receive at the end: the source, the instructions to build it, and a list of what is inside it?\nAnd how will the supplier keep it secure? NIST's Secure Software Development Framework exists partly\nfor that second conversation: it gives buyers and suppliers a shared vocabulary for development\npractices. For the first, an NTIA report defines a software bill of materials as \"a formal record\ncontaining the details and supply chain relationships of various components used in building\nsoftware\". Asking for one is a cheap way to see how much of what you are paying for was written by\nsomeone else.\n\n## What it looks like in practice\n\nKnowing what shipped is the part teams skip. On one platform the security work was moved from\nopinion into the build: in a\n[continuous security programme](/portfolio/ran-a-continuous-security-scanning-programme/),\na software bill of materials is generated on every build with Anchore and Syft, Dependabot watches\n6 ecosystems, CodeQL and ZAP analyse the code and the running instance, and even the outside steps\nof the build are frozen: each third-party workflow Action is referenced by its commit hash, which\nnobody can shift the way a tag can be shifted. Next to the automation sit 21 written security\naudits, including a threat model. A vulnerability recognised by the configured checks can fail the build. Its price is the volume of findings, which needs triage that never ends.\n\nGetting software from a change to production is the other half. Where releases had depended on\nsomeone remembering a sequence of manual steps, and doing it slightly differently each time,\n[automating build, test and deployment saved an estimated 4,000 hours](/portfolio/streamlined-ci-cd-processes-saving-4000-hours/)\nand made releases faster and more reliable. The gain came from the path being identical every time\nrather than from anyone being more careful.\n\nAnd the line between software and hardware is a practical one on a repair bench.\n[Laptop repairs](/portfolio/diagnosed-and-repaired-laptop-hardware/)\ncovered screens, hinges, keyboards and motherboards, and software problems across Linux, Windows\nand Mac. A laptop that will not power on could be the charger, the board or the battery, so the\nwork started with finding the real fault before touching anything.\n\n## Where it goes wrong\n\n### An advisory turns into a week of archaeology\n\nA vulnerability is announced in a widely used component, and nobody can say which of the\norganisation's systems contain it. The inventory only ever existed in people's heads and in lock\nfiles nobody reads, so it has to be reconstructed under pressure, system by system. Generate a bill\nof materials as part of every build and keep it with the release it describes. The question \"are we\naffected?\" then becomes a search.\n\n### Releases depend on who does them\n\nThe deploy works when one person runs it and breaks when another does, and the difference turns out\nto be a step that lives in somebody's memory. Each release is a small improvisation. Put the whole\npath into an automated job that builds, tests and deploys the same way every time, and treat any\nmanual step that remains as a defect to remove.\n\n### The budget stops at launch\n\nTwo or three years in, every update feels risky, the framework is several major versions behind,\nand the only proposal on the table is a rewrite. The software was paid for like a building and then\nleft alone, while everything around it kept moving. Keep a standing allowance for maintenance,\nupgrade dependencies in small regular steps while each step is still small, and expect the\nplatforms underneath to change on their own schedule.\n\n### A name stays fixed while the code behind it changes\n\nThe same build produces different results on two days with no commit in between. Somewhere a\nreference points to a moving target: a version range, a `latest` tag, a CI action referenced by a\ntag that its owner can re-point. Pin third-party code to an exact version or, where tags can move,\nto a commit hash, commit the lock file, and let a bot propose the updates so that every change\narrives as a reviewable diff.\n\n## Further reading\n\n- [NIST CSRC Glossary: software](https://csrc.nist.gov/glossary/term/software) — the definitions\n  NIST publications use, including the one that separates software from firmware.\n- [NIST SP 800-218, Secure Software Development Framework](https://csrc.nist.gov/pubs/sp/800/218/final)\n  — a core set of practices for building software with fewer vulnerabilities, written so that\n  buyers can use it with suppliers.\n- [NTIA: The Minimum Elements for a Software Bill of Materials](https://www.ntia.gov/report/2021/minimum-elements-software-bill-materials-sbom)\n  — what a list of the components inside a piece of software has to record to be useful.\n- [The Open Source Definition](https://opensource.org/osd) — the ten criteria a licence must meet\n  before software released under it counts as open source.\n\n\u003chttps://engineer.company/glossary/software/\u003e\n","date_modified":"2026-11-12T05:34:23Z","description":"What counts as software, where it stops and hardware begins, why owning it is a running cost, and how to know what you actually shipped.","formats":{"gemtext":"https://engineer.company/glossary/software/index.gmi","gopher":"https://engineer.company/glossary/software/gophermap","html":"https://engineer.company/glossary/software/","json":"https://engineer.company/glossary/software/index.json","markdown":"https://engineer.company/glossary/software/index.md","pdf":"https://engineer.company/glossary/software/index.pdf"},"kind":"page","language":"en","title":"What is software?","url":"https://engineer.company/glossary/software/","version":1}