Article
What a weekly release rhythm looks like with a remote developer
By Adil Soukaini
, 1 min read
When you hire a remote developer, the hardest part isn’t the code. It’s knowing what is happening between two calls. A fixed weekly rhythm answers that question before you have to ask it.
Monday: agree the week’s goals
The week starts with a short call. You and your developer agree what should be live by Friday: a feature, a set of bug fixes, or a step towards a larger release. Anything too big for one week is split into pieces that each work on their own.
Midweek: a preview link
Halfway through the week you get a link to try what’s in progress. You click through it like a user would, and you say what feels wrong while it is still cheap to change.
Friday: release, with notes in plain language
On Friday the work goes live, with release notes written for you rather than for developers: what changed, what to check, and what’s next.
Your code stays yours
The code lives in your repository from day one. You can see every change, and nothing depends on access you don’t control.
What you need on your side
- One person who can decide what matters this week.
- Access to your repository and hosting (or a fresh one, set up together).
- About 30 minutes on Monday and a few minutes to try the preview.
When it isn’t the right fit
A weekly rhythm suits ongoing product work. It is the wrong tool if you need a one-off fix, if there’s no clear product goal yet, or if you need a full-time team on site.
The same rhythm on our own products
ShipFastDev uses the same rhythm on its own products. In week 39 of 2026, live ships and satellites joined aircraft on SkyEye’s 3D globe; in week 40, its assistant JARVIS learned to present the news on the globe. The shipping log on the home page lists those releases.
