code once, ship twice
starting a project often means choosing a tech stack, framework, and other settings. this takes time, while others are already delivering their work.
to avoid this, you can:
- use github template repositories
- deploy quickly with nextjs and netlify
- follow a stepping stone approach for multiple projects
- have replicable devops setups like azure resource groups
think about how to repurpose work from failed projects for new ones.
online products, like information products, community access, media, software, physical goods, and services, often have similar delivery methods.
if delivery methods are the same, your process should be consistent.
the final product matters, not the unique process behind it.
tl;dr: focus on reusing and delivering, not on creating something unique every time.