rcgonzalezf/Answers for Exercises

## Answers for Exercises
You should check the definition of the authors, I'm sharing my answers here to generate discussion if you think is worth it.
The questions are on page 43 of my edition this might be different on your edition,
I'll only post my answers so please check the questions on the book.

1. Split2 is more orthogonal because it hides the details of the implementation to its consumers.

2. Modeless in general are less dependant of the context so for me this is more orthogonal, and usually a modal dialog depends on the actions or state of the caller, so if you change the caller code or the actions the caller can perform the modal dialog might have to be updated too, leading this type of dialog to be less orthogonal.

3. I'll say procedural,... In theory Object Oriented technology is more orthogonal because it hides the implementation and the state of the code, in procedural more often when you change one of the dependencies it might lead to an undesired impact on the program overall.
At the end in my point of view it depends on the design rather than the paradigm itself, you can create simple and straight procedural programs that can live independently and you can easily create tightly coupled object oriented programs.

What are your thoughts?
	You should check the definition of the authors, I'm sharing my answers here to generate discussion if you think is worth it.
	The questions are on page 43 of my edition this might be different on your edition,
	I'll only post my answers so please check the questions on the book.

	1. Split2 is more orthogonal because it hides the details of the implementation to its consumers.

	2. Modeless in general are less dependant of the context so for me this is more orthogonal, and usually a modal dialog depends on the actions or state of the caller, so if you change the caller code or the actions the caller can perform the modal dialog might have to be updated too, leading this type of dialog to be less orthogonal.

	3. I'll say procedural,... In theory Object Oriented technology is more orthogonal because it hides the implementation and the state of the code, in procedural more often when you change one of the dependencies it might lead to an undesired impact on the program overall.
	At the end in my point of view it depends on the design rather than the paradigm itself, you can create simple and straight procedural programs that can live independently and you can easily create tightly coupled object oriented programs.

	What are your thoughts?