# Software · Malte Therkildsen

> The engines and products I have built that run, each with its piece in the Lab, its case or its post. Every engine is checked against a reference such as SQLite, Git or LibreOffice.

Source: https://therkildsen.dev/software

Software 16

# Why I build engines from nothing

Sixteen engines, each written from its specification and checked against a program people already use. Each one below says what it is, what it shows and where you meet it in an ordinary project.

An engine is the hard version of a job your project also has. A regex engine is the search box and the form check, a layout engine is the page and the PDF, and a database is where your customers’ data is kept.

I write each engine from its specification and check every answer against a program people already use, such as SQLite, Git or Chromium. When your site is slow, breaks in one browser or needs something no library does, I look for the cause in the layer below instead of working around it.

[4 engines on your own file](#own-file)[8 engines in the Lab](#lab-engines)[8 engines in Writing](#post-engines)[12 jobs and their proofs](#jobs-sec)[30 everyday prototypes](#protos-sec)

Try it 4

## Try it on your own file

Drop a spreadsheet, a PDF or a PNG. The engine I wrote for that format reads it here in your browser, and each answer is held against a program you already use. The file is not sent to a server.

See the same engine turn a price spreadsheet into the page customers use.[Case No. 01, an example](https://therkildsen.dev/example)

In the Lab 8

## Engines you can run in the browser

Engines from nothing 8

## Engines with a post about each

Your job 12

## Start from the job you need done

Each row is a job clients ask for, and the engines and prototypes on this site that show I can do it. Press one to open it.

Prototypes 30

## Everyday prototypes by the job they answer

The first line of each prototype is what you get from it, and each one opens in the Lab on therkildsen.dev.