# CI Tooling Burden on Small Development Teams

DevFeed: [CI Tooling Burden on Small Development Teams](<https://devfeed.tech/articles/abandon-jenkins-for-great-good-29348.md>)

Original publisher: [Read original article](<https://arturdryomov.dev/posts/abandon-jenkins/>)

Author: Artur Dryomov

Published: 2018-12-09T00:00:00Z

Content type: opinion

Language: en

Sources: [Artur Dryomov](<https://devfeed.tech/sources/artur-dryomov.md>)

Topics: [ci](<https://devfeed.tech/topics/ci.md>), [Tooling](<https://devfeed.tech/topics/tooling.md>), [Developer experience](<https://devfeed.tech/topics/developer-experience.md>)

Tags: [ci](<https://devfeed.tech/tags/ci.md>), [developer-experience](<https://devfeed.tech/tags/developer-experience.md>), [tooling](<https://devfeed.tech/tags/tooling.md>)

## AI overview

An opinion piece about the operational burden of CI, builds, scripts, and related tooling on small software teams. It argues that concentrating this work in one developer creates a bus-factor risk and can pull that developer away from product work.

## Source excerpt

CI and CD techniques are a part of all good happened to the software development. Having CI in place means better productivity and higher confidence in the result of the everyday work. Sounds kind of obvious, right? Well, let's take a look at the dark side of the Moon. Do you have a person on the team who occasionally curses Gradle or (and) Maven, Android SDK or (and) NDK? Maybe someone who knows everything about these weird Shell scripts you have in the repository? You know, the one who doesn't like mentions about broken nightly builds, looks at the htop from time to time? Yeah, the tooling person. The fancy name nowadays is a Developer Experience Engineer. Right. The question is -- do you want to be this person? No worries -- I already know the answer.