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.
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