Aqui les presento una lista de los comentarios que me parecen interesantes:
- I don't think that it should be possible to graduate with a computer science, computer engineering, etc. degree without having used the basic tools (compilers, editors, debuggers, linkers, version control systems and so on) for a couple of major projects.
- The use of tools must not be a substitute for a good understanding of the principles of programming.
- Let me point to algorithms, data structures, and machine architecture as essentials. I'd also like to see a good understanding of operating systems and networking.
- Think. Discuss with colleagues and potential users. Get a good first-order understanding of the problem domain. If possible, try to be a user of an existing system in that field. Then, without too much further agonizing, try to build a simplified system to try out the fundamental ideas of a design.
- I don't think it's the features that are hard to learn, it is the understanding of the programming paradigms that cause trouble.
- Learn to use the language features to solve simple programs at first.
- I saw so many students who simply didn't have the notion that code itself is a topic of interest and that well-structured code is a major time saver... I heavily emphasize structure, correctness, and define the purpose of the course as "becoming able to produce code good enough for the use of others."
- You need to give the students a feel of the machine as well as the mechanisms to make the (correct) use of the machine simple.
Y para finalizar, como me dijo alguna vez mi profesor de C++: "escribir codigo es como escribir poesia".
Seria interesante saber que opinan al respecto los profesores de las universidades en el Peru y Latinoamerica, y otros experimentados programadores tambien, no?
Gracias por leer.
No comments:
Post a Comment