are you reading changelog updates of other companies' products? if so, why?

Jakob Engelhardt
4 replies

Replies

André J
Sure. It's a quick way to gauge if a product has the momentum it needs to be sustainable in the future. Especially new ones. or even old ones. If someone is still working on it. I was looking at swift lints changing the other day. They stopped using their approved apple developer to sign their releases 2 years ago. Then I'm like okay. Maybe not over invest in adding SwiftLint to my CI / release infra.
Share
Jakob Engelhardt
@sentry_co ah yea that’s a great example
Share
Jakob Engelhardt
@sentry_co is there a specific changelog you follow just out of curiosity?
André J
@jakob_engelhardt1 Uhm not exactly follow over time, but I did a lot of research on them. How to design good ones and what to avoid. what language to use. They are tied very strongly to product development. It's a fascinating field actually. Related to release notes / app versioning. It's also interesting to watch the life times of software. How they start, how they fail or thrive. open source projects for instance. Like Mozilla has a lot of these, you can even dive into their issue trackers, where they do allot of their team collaboration. You can see how they tackle problems. And collaborate. How they communicate and then how they sunset things and move on etc. It grounds you in a way to be realistic when you your self builds something. Okay is this a short burst thing, or is this for the long run etc. Changes your perspective on business strategy.