THE DEVELOPER IS DEAD,
LONG LIVE THE DEVELOPER.
The promise of AI to automate the work of developers is said to be here. But what does it really look like right now and how soon will it live up to its promise to slash build times and costs - or more importantly, produce successful project outcomes? This white paper examines what's actionable now to achieve both and when in the future an "AI Platform" will contribute to those outcomes by replacing the role of the developer.

Co-pilots will eventually improve program velocity, but will they change fundamental program team structures or development cycles? Before co-pilots become solo pilots, how much training and compute power will the robot require to replace the role of the developer, engineer, architect, or scrum master? Before these possibilities are real enough to be priced into our delivery costs or impact economics of our industry, best-practices and team role behaviors will need to be narrowly defined or project outcomes leveraging generative AI in the future will be just as costly and unreliable as they are today.

Building on research about why projects fail and a point in time snapshot of the cresting AI hype, this white-paper plots both against narrowly defined practices and procedures. The results give visibility to a DevOps design pattern predicated on the notion of an automation platform capable of producing reliable and high-performance project outcomes.

If you'd like to know more about this research, have some input of the topic or would like to recieve an advance copy of the white-paper, please email me at mccaheyw@outlook.com or book an appointment.

Best regards,
--Bill