I am less than a month away from releasing a 200+ pages book where I discuss exactly that question :-). From git init to production and anything in between. It's called Cloud Native Web Development and if you're interested, head over to gum.co/cloud-native-web-development for a full table of contents and more details.
At a high-level, I'd focus on removing friction for the dev team, automating what can be automated, focus on testing and quick, frequent production deployments using feature toggles to guard unfinished code from running in production.
One area that often causes friction is setting up a project's development environment. I'd personally use gitpod.io (Why I use a cloud-based development environment and how you can too) so that developers on the team can click a link and start up a fully configured environment.
Another area is CI / CD. I'd develop that pipeline as early as possible when it's still very simple to do. Then as the project grows, the CI / CD configuration grows with it organically.
I am less than a month away from releasing a 200+ pages book where I discuss exactly that question :-). From
git initto production and anything in between. It's called Cloud Native Web Development and if you're interested, head over to gum.co/cloud-native-web-development for a full table of contents and more details.At a high-level, I'd focus on removing friction for the dev team, automating what can be automated, focus on testing and quick, frequent production deployments using feature toggles to guard unfinished code from running in production.
Nice coincidence :) Good luck on your book.
How would you remove friction?
Good question, let me specify that a bit better.
One area that often causes friction is setting up a project's development environment. I'd personally use gitpod.io (Why I use a cloud-based development environment and how you can too) so that developers on the team can click a link and start up a fully configured environment.
Another area is CI / CD. I'd develop that pipeline as early as possible when it's still very simple to do. Then as the project grows, the CI / CD configuration grows with it organically.
Never thought to use gitpod this way. For most companies cloud IDEs are a no-go. Nice tips :)
Even if it's self-hosted as per gitpod.io/self-hosted?
I understand the concerns when it's used a SaaS offering.
I didnt know that option. That sounds better indeed