Five Checks Before Building on an Inherited AppFive Checks Before Building on an Inherited App
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
What I Check First in Someone Else's Code
When a founder hands me an app another developer built, the first request is usually a new feature. I don't start there. Before I add anything, I check these five things:
Can it run on a fresh machine? If nobody can set it up without the original developer, every change will be slow and risky. I write down the setup steps, env variables and seed data first.
Where are the secrets? API keys hardcoded in the code, or sitting in the git history, are one leaked repo away from a very bad day. They go into environment variables and get rotated.
Do the backups actually restore? Plenty of apps have backups. Far fewer have ever restored one. A backup nobody has tested isn't a backup.
What happens when it errors? If errors go nowhere, the users are your monitoring. Logs and alerts come before any new code.
How healthy is the database? Missing indexes, no foreign keys and slow queries are fine with a few users and painful once the app grows.
None of this is exciting, and it won't show up in a demo. But it's the difference between building on solid ground and building on someone else's shortcuts.
Inherited an app and not sure what state it's in? Book a free build audit: calendly.com/roshaanali-business
Post image
Back to feed
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started