Dealing With Complexity
I had an interesting talk and two teachers in the last week. A chair of a country of computer science
Teachers in universities and other technical high school/career. We are talking about how to start programmingMicrosoft Office 2010 is so great.
Students in their plan. I said, I see again and again the students are nested loops and repair
The ring, until they get a random clean compiler. Then they often surprised that code without work
They expected. Others said, this problem from students to write many code
Once more than work.
For example, a teacher is using the Alice is a great tool. But many students began to add them all
Think they need immediate trouble, let them all the way to work. The university professorOffice 2010 is my favorite.
Students try to write all the methods and functional test project and to any part of the first. Final results
Is the code, it is impossible for the error is discovered there debugging very difficult.
Students want instant results. They think they can make more details on their heads, they will often.
Maybe it from multitasking so much. Maybe it's just young vanity. Or maybe because they see othersMicrosoft outlook 2010 is convenient!
Keep the details of their head, in their teacher (perhaps) and assume that it is easy. Now many students think they
Clever than their teachers or more knowledge. Usually they are wrong. They don't know
The teacher gave them the practice and experience, only one side will make their practice to catch up.
I think we all tried to let the student to break down into small pieces. We emphasize modular and methodsOutlook 2010 is powerful.
And function. We talked a lot about the top-down design we broke the big problems in small pieces, gradually. I
If we don't want to talk about always get enough each small work, to enter the next one. weOffice 2007 can make life more better and easier.
Talk about unit testing? We have enough to maintain it simple enough?Microsoft Office is helpful.