Adyakshar Labs

Adyakshar Labs / Blog

Engineering Management

What Ada Lovelace Can Teach Us About Specifying Software

Illustrated portrait of Ada Lovelace

Ada Lovelace Day, observed on the second Tuesday of October, celebrates women in science and technology. Her story also carries a practical lesson for founders and managers who commission software.

What she did

In 1843, Ada Lovelace published an English translation of an article about Charles Babbage's proposed Analytical Engine. She added her own notes, which grew to roughly three times the length of the original article. Within them is a method for computing Bernoulli numbers, often described as the first published computer program.

The lesson: purpose before mechanism

Her notes are remembered not only for the method but for the question behind them: what could such a machine be for? She was thinking about purpose before the machine existed.

Most software projects that go wrong skip this step. They start with technology choices or a feature list and discover later that no one agreed on what the product was supposed to achieve.

Four questions to ask before you build

  1. Who is this for? Name a person or a role, not "users".
  2. What should they be able to do? One sentence, with a verb.
  3. How will we know it works? A result you can check, not a feeling.
  4. What are we not building yet? Edges are cheaper to draw early.

Write the specification as if someone else will build it

Lovelace's notes were detailed enough for another person to follow. A good project brief should be as well: clear enough that an engineer who was not in the room can start with confidence, and a manager can tell when the work is done.

Start with the question

At Adyakshar Labs, we begin projects with questions like these, then take them from idea to working product with clear communication and honest timelines.

Have a project in mind? Get in touch at info@adyaksharlabs.com or visit adyaksharlabs.com.

  • ada lovelace day
  • software specification
  • project management
  • software development
  • adyakshar labs

Keep reading

Engineering Management · 4 min read

The Small Change That Was Not Small

Every team has heard "it's just a small change." Here is what that sentence usually means, why it keeps costing money, and three questions that make a small change honestly small.

From across the family

More reading from the other Adyakshar Labs products.

Bindus
How Long Did That Job Really Take? Using Time Sheets and Milestones HonestlyMost small teams quote from memory and learn the real number after the job is done. A simple habit with time sheets and milestones makes the next quote better than the last.
Sampad AI
What to Do in the First Two Days After a Tax Notice ArrivesA tax notice rarely gets worse in two days. It gets worse when it sits. A short checklist for capturing the facts, updating the client and planning the reply.
Quantum Labs
Harvest Now, Decrypt Later: How to Decide What to Protect FirstEncrypted data can be recorded today and read later. You cannot protect everything at once, so sort it by shelf life. A plain test and a three-tier list for deciding what comes first.