Resources - Everything I have written down
How the work is actually done, at enough depth to judge it before hiring anyone. Then the same subjects in plain language for an owner who built the application themselves, and the documents for your own project.
Building and running software
Written for a developer or a lead. How the work is actually done, so you can judge the depth before hiring anyone.
-
Azure DevOps pipelines for a .NET application
Replacing a manual release with a pipeline: build once and deploy that artifact everywhere, an identity instead of a secret, running EF Core migrations without taking the site down, and a release you can reverse.
Read the guide → -
Terraform for an Azure environment you already have
Putting a running environment under Terraform without an outage: remote state and why it holds your secrets in plaintext, importing what exists instead of rebuilding it, what Terraform must not own, and what to do when somebody changes something in the portal.
Read the guide → -
Knowing your .NET app is healthy after a deploy
The five alerts worth having and the ones that produce an inbox nobody reads, the Application Insights sampling default that makes your own queries lie, and why the daily ingestion cap goes blind on the worst possible day.
Read the guide → -
Making an inherited .NET codebase safe to change
The order to work in when the author has left: build from a clean checkout, get it into a pipeline, record what the code does before changing it, upgrade the framework one project at a time, and why the rewrite is almost never the answer.
Read the guide →
If you built it yourself
Written for an owner who built an application with an AI tool and is working out what comes next. Plain language, and honest about what you can do without hiring anyone.
-
What "production-ready" actually means
The nine gaps between an app that works and an app that holds up, what each costs you when it is missing, which of them you can honestly skip, and the three you can close yourself this week.
Read the guide → -
Why your AI-built app gets harder to change
The tool needs more tries, fixing one thing breaks another, and changes that work on your computer won't go live. What's happening, what you can do about it yourself, and how to tell when it is no longer a job for a tool.
Read the guide → -
When to move off Lovable Cloud, and when not to
The built-in hosting is good, and a lot of apps should stay on it. What it is good at, the handful of things that mean it is time to move, and how to tell which one you are.
Read the guide → -
What a customer's security review will ask you
The five questions it comes down to, what a good answer sounds like, and where apps built with AI tools usually come up short. Nobody asks which tool wrote your code.
Read the guide → -
Is Lovable HIPAA compliant?
No build tool is, and none can be. What HIPAA applies to, why the tool that wrote your code is rarely the deciding factor, and what you can check about your own app this week.
Read the guide → -
The FTC Safeguards Rule, for an app you built yourself
What the rule asks of accountants, tax preparers, advisers and insurance agents. Which parts are engineering, which stay with you, and the three things worth doing first.
Read the guide →
Your project
The documents for working together: how an engagement runs, what you receive at the end, and how your work is kept secure.
-
How a deployment works
The three milestones a deployment is delivered in, what you get at each one, and what is included.
See the process → -
Example handover
An anonymized example of the written handover you receive when your app goes live, covering every account, password, and security setting.
View the example → -
Security & trust
How your app, your cloud account, and your data are kept secure. I take only the access the work needs, and you can withdraw all of it the day we finish.
Read more → -
How access to your work is controlled
For whoever at your firm signs off on outside vendors. Who can sign in to your private client area, what one person can reach, the record kept of every document opened, and what is not audited or certified.
Read the document → -
Azure setup guide
A short, one-time checklist to set up your Azure account and grant the access I need before your deployment begins.
Read the guide →
Twenty minutes, and nothing to prepare.
Tell me what you need built or fixed, and I'll tell you where I'd start.