--- > **For build tools** (tools compile software changes into executable binaries), the highest priority adoption factor is whether the tool is highly configurable. - [View Highlight](https://read.readwise.io/read/01h4jpar77e62drpb3r7gd62ke) --- > **For continuous integration tools** (tools integrate software changes into the shared mainline of the software), the highest priority adoption factor is whether the tool is compatible with the technologies developers use. - [View Highlight](https://read.readwise.io/read/01h4jpb0av5zyt771c5zf1drd6) --- > **For infrastructure as code tools** (tools that manage configuration options of the software as well as configure the deployment environment), the highest priority adoption factor is how visible the usage of the tool is within the organization. - [View Highlight](https://read.readwise.io/read/01h4jpb66g8p4egs6e602r4g5c) --- > **For version control tools** (tools that manage all the changes of artifacts related to the software of interest), the highest priority adoption factor is whether the tool fits well with the way developers work. - [View Highlight](https://read.readwise.io/read/01h4jpbcw23n04qejhvbxx8ss8) --- > This paper further supports the need for platform teams to understand developers’ existing workflows before designing solutions. While many tooling owners look to education-related strategies to improve adoption, this study suggests that they should consider iterating on tools so they fit how developers work, as well as make tools more visible amongst developers’ peers. - [View Highlight](https://read.readwise.io/read/01h4jpczhpymaqyveqgfyys6h2) ---