I don't agree on the flow diagram, which when the requirements changed that we "throw it all out and start over". If the code is broken down well, not all things are discarded. if the requirements that got changed is isolated separately, that is the only part that got changed. #Changeability
Head of Product at Temporal. Previously lead architect and low-level systems programmer for scale out SaaS offering. Game engine developer, ML engineering expert. DMs open on Twitter.
I don't agree on the flow diagram, which when the requirements changed that we "throw it all out and start over". If the code is broken down well, not all things are discarded. if the requirements that got changed is isolated separately, that is the only part that got changed. #Changeability
It wasn't intended to be a good example. I also don't agree with it, which I think the article makes pretty clear.