Software Development for Non-Engineers

(Pro Version)

What’s Actually Under the Hood

You’ve built the app. The depreciation calculator works. The variance flagger catches the right exceptions. It runs on your machine and does exactly what you need.

Now what?

The gap between “it works on my laptop” and “the team can use this” is where most vibe-coded finance tools go to die. Not because the logic is wrong. Because nobody thought about where the thing lives, who can access it, what happens when two people use it at once, or what breaks when your Python version updates.

This section is a plain-language map of the software development stack. Not so you can become an engineer. So you can stop nodding politely in meetings with engineers and start asking the questions that matter.

Think of this the way a good engineer would think about our world. They don’t need to pass the CPA exam. But if they’re building a tool that touches your GL, they’d better understand what a chart of accounts is and why you can’t just rename line items on a whim. Same principle, reversed.

Version Control: The Audit Trail for Code

You already understand version control. You just call it something different.

Every time you lock a workbook before close, save a dated copy of a forecast, or track changes in a Word doc before sending it to legal, you’re doing version control. Poorly, usually, but the instinct is right.

Git is the system developers use to solve this properly. It tracks every change to every file, who made it, when, and why. GitHub is the platform where those repositories (repos) live. Think of Git as the journal entry and GitHub as the general ledger.

Your app has to run somewhere.
On your laptop, it’s a prototype.
In production, it needs infrastructure.

A few concepts worth knowing: