> When there are expected dimensions of software change, it can be worth paying the cost to create software with higher flexibility. Flexible software is harder

> When there are expected dimensions of software change, it can be worth paying the cost to create software with higher flexibility. Flexible software is harder to create, more complex, harder to understand, and harder to maintain. I agree with what is being said, but the way it is coming across doesn't work for me - I had to go back to the first sentence because the "harder to maintain" confused me: What is maintenance if not making changes? If so, flexible (less coupled) software is easier to maintain (over time). But the author's central point feels correct: flexible software is requires more effort to think of writing in that way. What definitions of "maintenance" and "complex" is the author using and how are they different from mine?