Project setup - Do you make project setup as easy as possible?

Last updated by Tiago Araújo [SSW] about 1 year ago.See history

Developers understand the importance of the F5 experience. Sadly, lots of projects are missing key details that are needed to make setup easy.

Let's look at the ways to optimize the experience. There are 4 levels of experience that can be delivered to new developers on a project:

Level 1: Step by step documentation

This is the most important milestone to reach because it contains the bare minimum to inform developers about how to run a project.

The rule on awesome documentation teaches us all the documents needed for a project and how to struture them.

The and are the core documents that are essential for devs to get running on a project.

Bad example - A project without instructions

Good example - A project with instructions

::: greybox Tip: In addition to pre-requisites, make sure to mention what isn't supported and any other problems that might come up.

E.g. Problems to check for:

  • Windows 8 not supported
  • Latest backup of the database
  • npm version :::

Tip: Don't forget about the database, your developers need to know how to work with the database

Figure: Don't forget about the database!

Level 2: Less documentation using a PowerShell script

A perfect solution would need no static documentation. Perfect code would be so self-explanatory that it did not need comments. The same rule applies with instructions on how to get the solution compiling. A PowerShell script is the first step towards this nirvana.

Note: You should be able to get latest and compile within 1 minute. Also, a developer machine should not have to be on the domain (to support external consultants)

All manual workstation setup steps should be scripted with PowerShell, as per the below example:

PS C:\Code\Northwind> **.\Setup-Environment.ps1**

Problem: Azure environment variable run state directory is not configured \_CSRUN\_STATE\_DIRECTORY.

Problem: Azure Storage Service is not running. Launch the development fabric by starting the solution.

WARNING: Abandoning remainder of script due to critical failures.

To try and automatically resolve the problems found, re-run the script with a -Fix flag.

Figure: Good example - A PowerShell script removes human error and identifies problems in the devs environment so they can be fixed

Level 3: Less maintenance using Docker containerization

docker logo
Figure: Docker Logo

PowerShell scripts are cool, but they can be difficult to maintain and they cannot account for all the differences within each developers environment. This problem is exacerbated when a developer comes back to a project after a long time away.

Docker can solve this problem and make the experience even better for your developers. Docker containerization helps to standardize development environments. By using docker containers developers won't need to worry about the technologies and versions installed on their device. Everything will be set up for them at the click of a button.

Learn more: Project setup - Do you use Docker to containerize your SQL Server environment?

Level 4: More standardization using dev containers

Dev containers take the whole idea of docker containerization to another level. By setting up a repo to have the right configuration, the dev team can be certain that every developer is going to get the exact same experience.

Learn more: Project setup - Do you containerize your dev environment?

Figure: Good example - After using dev containers you would be as happy as Larry!

Adam Cogan
Piers Sinclair
Ryan Tee
Adam Stephensen
We open source. Powered by GitHub