Peak DevOps will create a pivotal moment of transition for the developer industry leading to a 3rd Wave of Software Industrialization defined by a multi-trillion dollar Autonomous Development landscape.
I have a little question, under what segmentation in your landscape would you put dev tools that help to get context for code lines in the IDE such as CodeStream (acquired by New Relic, Codex etc.?
Thank you so much for the analysis, it's very interesting!
In 7.2.1 you seem to have pasted a comment from a reviewer. In 7.7.3 you have written "June 202" rather than 2022. I noticed other typography errors too, but they were less important.
Great analysis and writing throughout though. It was a long slog, but I think I agree with almost everything you've said here and I've been predicting the same trajectory for the industry for some time.
You had my full attention starting from the XYCD cartoon at the begining of your paper. I am caught up in this cartoon in a real-life project just now. After considering details at each step in your paper I see many ramps from which to step off my "automation" project, from using github to let others step up to improve code if the tool's vision really does a good job automating something, all the way up to a machine code option to finally request a bot to do this work from common inputs. Nicely done Tyler.
you called it Tyler back in 2022!
Hi Tyler, I love reading your articles!
I have a little question, under what segmentation in your landscape would you put dev tools that help to get context for code lines in the IDE such as CodeStream (acquired by New Relic, Codex etc.?
Thank you so much for the analysis, it's very interesting!
There is a public version of the sheet where you can search for different companies and products to see how they are placed into different segments.
https://docs.google.com/spreadsheets/d/1M_LFJ6DxBmlkuQuipVwA9qBWRMm6Z7M1zJ1EONe6K-I/edit#gid=2068363245
Thank you so much for your quick response!
Hello from Melbourne, Australia.
Elen
In 7.2.1 you seem to have pasted a comment from a reviewer. In 7.7.3 you have written "June 202" rather than 2022. I noticed other typography errors too, but they were less important.
Great analysis and writing throughout though. It was a long slog, but I think I agree with almost everything you've said here and I've been predicting the same trajectory for the industry for some time.
Just wanted to thank you for the depth of your research. I haven’t seen anything equivalent so far out there. Many thanks 🙏
You had my full attention starting from the XYCD cartoon at the begining of your paper. I am caught up in this cartoon in a real-life project just now. After considering details at each step in your paper I see many ramps from which to step off my "automation" project, from using github to let others step up to improve code if the tool's vision really does a good job automating something, all the way up to a machine code option to finally request a bot to do this work from common inputs. Nicely done Tyler.