This entry is part of the πNotebook β an exclusive, subscriber-only section of SoftwareResilience.com, offering a glimpse into my working notes, raw observations, and the formative thinking that underpins my published work. If you find these insights useful, I would be grateful if you considered subscribing or recommending the Notebook to a colleague.
π¬ All content here is crafted by hand β no automation, no AI-generated filler. π¬
β¦and now back to our notes.
#1
Dev Interrupted research: We broke the software delivery process into 14 steps across planning, requirements gathering, coding, and release. We asked participants to consider their most recent pull requests, and for each step of the process, we asked participants who completed the task: a human, AI, or both.
Coding phase shows strong AI integration
Regarding writing code, only 33% of developers rely solely on humans, while 67% use AI either wholly or partially.
AI is most dominant in writing tests, with 24% of tests being AI driven.
Even pull request descriptions have seen high AI adoption, with 53% of teams using AI assistance.