Where Does Your Code Actually Live?

I asked a new client for access to their code so I could pick up where the last developer left off. There was a long pause. They didn't have it. They weren't even sure what it was, or that it was a thing they were supposed to have.

Their site was live and working, so this had never come up. It doesn't, until the day it has to, and by then the person who holds the code is usually someone you're no longer talking to.

So here's the piece nobody hands owners on day one: the code your business runs on is a thing you can hold, and holding it is not the same as your site being online.

The site being up doesn't mean you have the code

This is the part that trips people up, so it's worth saying plainly. Your website being live and your having the code are two separate facts, and you can have the first without the second.

Think of it like a building. The site being up is the building being open, with the lights on and customers walking in. The code is the blueprints and the keys. You can walk into a shop every day for years without ever holding the blueprints to it. It works fine, right up until you need to change something structural, or the person who does hold the blueprints stops answering the phone.

The code is the actual instructions your site is built from. Every developer who works on it needs it, the way a contractor needs the plans. If those instructions only exist on one person's laptop, or in an account only they can log into, then whatever the site looks like from the front, you don't have your building's blueprints. Someone else does.

Where it's supposed to live

Code lives in something called a repository, or "repo." Don't worry about the word. Picture a shared vault that holds the current version of the instructions plus the whole history of every change ever made to them, who changed what, and when.

That vault usually sits on a service like GitHub or GitLab. The only question that matters to you is whose account it lives in. If the repo is in an account that belongs to you or your company, you're holding the blueprints. If it lives only in your developer's personal account, they are, and you're renting access to your own building without knowing it. It runs fine either way, right up until the account it depends on turns out not to be one you control.

Why the history is the valuable part

It's tempting to think the code is just a folder of files someone could email you, and technically the latest version is. But the reason a repo matters is the history, and the history is the part that quietly protects you.

That record of every change is what lets the next developer understand what was done and why, undo a mistake without redoing everything, and see how the thing was actually built instead of guessing. A developer who hands the next one a live repo with its full history is handing over a map. A developer who hands over a zip file of the latest files is handing over a snapshot with the map torn off. It'll work, but everyone who touches it afterward pays for what's missing, and you pay for their time.

What "having your code" actually means

So if you want to know whether you've got your code, it's not one question, it's three, and they're small.

Is there a repository at all, rather than the only copy sitting on someone's laptop? A single laptop is one dropped coffee away from your business.

Is it in an account you own or can be made an owner of, not only your developer's personal one?

And could a new developer be given access to it tomorrow without needing the last one's cooperation? Because the day you need that is often the day you and the last developer aren't on speaking terms.

You don't have to read a line of it or ever open the thing yourself. You just need it to live somewhere you control, so that the day you hire your next developer, it's a handoff and not a salvage operation. That single difference, whether the next person inherits a map or has to reconstruct one, is the whole reason this is worth sorting out now, while the site is calm and the last developer still answers email.