Why is the second part of the course "Defining Problems"? Well, to emphasize that we programmers need that whatever we are going to program, in the broadest sense of this word, be correctly and completely defined even before we start programming as such to avoid misunderstandings that will imply bad or incomplete results, and that it is also necessary that before changing something and considering it final, they also have to count on us.

And today, as there is no human activity (or robotics) that is not impregnated with programs for their total or partial execution, how does the world expect us programmers to understand everything at such a precise level as to be able to "program" where then Will the result of our programming be measured objectively, that is, with even numerical metrics being in turn "qualitative"?

To continue reading please click here.

Pin It

No thoughts on “1. Define Problems for Us. First part.”

Leave your comment

In reply to Some User