I feel like you get a flavor of this for software by reading the mailing lists in the more mature open source project, you can basically get a continuous flow o

I feel like you get a flavor of this for software by reading the mailing lists in the more mature open source project, you can basically get a continuous flow of analysis and build or rebuild. It's not packaged in a nice episodic report form, but you can get a little of that too with some projects. For the software industry as a whole, the closest thing might be the SEI[1], but that body of work takes some effort to work through, perhaps suffering a bit from a more adademic roots vs a more industry engineering info exchange approach like M&A. For that you might have specialist areas, for example, the Jepsen tests and blog[2]. [1] https://en.wikipedia.org/wiki/Software_Engineering_Institute https://en.wikipedia.org/wiki/Software_Engineering_Institute [2] https://aphyr.com/tags/Jepsen https://aphyr.com/tags/Jepsen