Services
Start a new project the right way
The first weeks decide whether year two is calm. Starting right means a repo, a way to run it, and a slice of product that is already real.
We set the project up so the second developer is not guessing. Conventions are written where the code is, in a few pages, not a wiki nobody opens.
When it fits
- A new product or service is about to get its first code.
- A second developer will join soon.
- You want CI and conventions from the first week, not after the first year.
How the work goes
- Repo, formatter, tests, and a local run that works on a clean machine.
- Environments are named. Secrets have a home that is not the chat history.
- CI runs from day one, even while the test suite is small.
- The first merge is a real slice: a page, an API, or a job. Review happens on that slice, so the habit exists before the codebase is large.
Example: open a week
First weeks
The first weeks are a sequence. Open one.
What you receive
- A repo a new teammate can run from the readme
- CI on day one, even if the suite is still small
- One reviewed slice of the product, already in main
How to start
Send what the project is, who will work on it, and where it should run. Email it to info@developerlab.nl, or see the contact page for other ways to reach Puya Sarmidani.
Send an email