The signal

An app can be cheap to start and expensive to keep healthy. That gap helps explain why businesses spend money on software maintenance and cybersecurity, not just shiny new features.

Much modern software is assembled using open-source components: code that people can inspect, use and adapt under its licence. These components can handle everyday jobs such as displaying a calendar or processing a file. Developers do not have to build every piece themselves.

But free to download does not mean free to look after. Components change, security weaknesses get discovered, and older versions stop being supported. Someone has to keep track.

For a 20-something, this is a useful correction to the idea that the whole tech economy revolves around launching the next big app. There is also work in keeping existing systems dependable. The Bureau of Labor Statistics identifies maintaining programs as part of software development and projects strong demand for information security analysts.

How it actually works

Think of an app as a café that buys ingredients from several suppliers. Making everything from scratch would be slow and costly. Buying ingredients saves effort, but the café still needs to check deliveries and respond when something is recalled.

Software components create a similar responsibility. A component your app relies on is called a dependency. That component may depend on other components, so the full chain can be longer than the developer initially sees.

When an update appears, a business has several jobs:

  • Notice it and understand whether it fixes a security problem, changes features or both.
  • Check whether the update works with the rest of the app.
  • Release the change carefully and watch for problems.

Automation can handle some of this. It can identify outdated components or propose an update. But a proposed change is not the same as a tested, safely released change.

That is where the spending goes: developer time, testing systems, security tools and sometimes outside support. A business may pay for help because an interrupted checkout or exposed customer record could cost much more than routine upkeep.

The economic lesson is simple: reducing the cost of building something does not remove the cost of owning it. Every useful app can bring a continuing maintenance obligation.

Real example

GitHub’s Dependabot is a concrete example of this maintenance work becoming automated. Its open-source engine checks dependency information and helps generate proposed updates. On GitHub, these proposals can appear as pull requests—suggested code changes that a project can review before accepting.

Imagine a small booking app that uses an outside component to read uploaded files. A newer version becomes available. Dependabot can propose updating the component instead of waiting for someone to remember to check it manually.

The team still needs to establish whether bookings and uploads work after the change. The tool reduces repetitive checking; it does not take responsibility for the business’s service.

This creates useful work around the tool: reviewing changes, maintaining tests, investigating failures and explaining which fixes need attention first. Those tasks may sit within software development, testing or security teams rather than a job called “dependency updater.”

It is not an instant route to a tech salary. Technical foundations and practice matter. Nor does growing demand make every software company a good investment. The practical opportunity is understanding a recurring business need, rather than chasing a fashionable label.

Your small move today

Spend 15 minutes making a three-line maintenance brief. Open the Dependabot repository linked below and skim its introductory explanation. Then write:

  • What repetitive task does this tool handle?
  • What still needs human checking?
  • What business problem could that checking prevent?

Use plain language, not copied jargon. You will have a small, concrete explanation of how a free tool supports paid work—and a better question to ask about any new app: who keeps it working after launch?

SOURCES
  1. 1GitHub — Dependabot Core
  2. 2U.S. Bureau of Labor Statistics — Software Developers, Quality Assurance Analysts, and Testers
  3. 3U.S. Bureau of Labor Statistics — Information Security Analysts

Drafted with AI from trusted public sources and checked against our editorial rules. Educational content only — not personalized investment advice. Investing has risks and returns are never guaranteed.