KISS principle & fluent builder pattern

[aminsharifi]

If it's good practice, may I do the same for the rest of the project's setters?

[KyleMcMaster]

I'm just curious as I try to understand the changes being proposed here. How does the KISS principle apply to having SetSomeProperty methods (potentially many methods if you're doing them individually)? Doesn't introducing setter methods make the Constructor, which itself is a setter, more complex?

[aminsharifi]

I'm just curious as I try to understand the changes being proposed here. How does the KISS principle apply to having SetSomeProperty methods (potentially many methods if you're doing them individually)? Doesn't introducing setter methods make the Constructor, which itself is a setter, more complex?

Hello Kyle,
Thanks for your review
I wanted to bring to your attention that three commits have been made with the intention of following the KISS, DRY, and CQRS principles. Regarding the first commit you mentioned, I agree that it may not fully adhere to the KISS principle, but it does demonstrate the DRY principle. Specifically, the line Guard.Against.NullOrEmpty(name, nameof(name)) appears to be duplicated in both the constructor and the UpdateName method.