lesson
25 min

Ship Small, and When Not to Code

Release software in small, safe steps, and choose between building, renting, and not coding at all.

What you will learn

By the end of this lesson, you can explain why teams release small changes and choose between building a tool, using an existing one, or not coding at all.

Ship small, safe, and often

Big releases are risky. If a hundred things change at once and something breaks, it is hard to find the cause. Small releases are easier to check and easier to undo.

Teams use CI/CD to help. CI (continuous integration) means tests run on every change. CD (continuous delivery) means changes that pass the tests can be released in small steps. You do not need to set this up yet. You need to know the habit: small change, run tests, release, watch.

Keep secrets out of code

A secret is a password, an API key, or anything that grants access. Never put secrets in your code or in a shared file. Store them in environment variables, which are settings kept on the computer that runs the code, outside the code itself. If a secret ever lands in a shared file, treat it as stolen and replace it.

Build, rent, or do not code

Not every problem needs new code. You have three choices.

ChoiceGood whenWatch out for
Do not codeA paper form, a phone call, or a shared spreadsheet already worksOutgrowing it without noticing
Use an existing toolA common problem, like scheduling or sign-ups, with well-known toolsData you cannot export, terms that change, too many features
Build your ownA unique need, a tool you want to own and control, or one that ties systems togetherSomeone must maintain it for years

Building means owning the code and the data. That gives control. It also gives responsibility: updates, security fixes, and someone who understands it after you leave.

Judgment check

Do not write code when:

  • Nobody will maintain it after the project ends.
  • A simple, existing tool solves the problem well.
  • The tool would make decisions about people, like who gets help, without a person reviewing.
  • You would need to collect sensitive data you cannot protect.

Prompt Lab

Use AI to compare build, rent, and no-code options, then make the final call yourself.

Who should the AI act as?

What exactly should it do?

What does it need to know?

What shape should the answer take?

How should it sound?

Your prompt

Act as a practical software advisor for small organizations.

Format: A table comparing do not code, use an existing tool, and build, with one maintenance risk each, then a recommendation

Do not paste private details (full name, address, ID numbers) into any AI tool.

Go deeper: Own the code: building internal tools over rented software

Quiz: Module 3 Quiz: Software Development

  1. 01What is an MVP?

    Choose one.

  2. 02What does a test do?

    Choose one.

  3. 03Where should a password or API key go?

    Choose one.

  4. 04What does the Knight Capital case teach?

    Choose one.

  5. 05When should you NOT write new code? Choose all that apply.

    Choose all that apply.

Ask. Answer. Build together.