Computational Thinking Guide
Brief Discription & Significance for
Computational Thinking
A
s far as I'm concerned,
CT is not merely a fundamental subject for dealing with computer science issues, but also a unique way to think,
to figure out how to solve the problem in our daily life, especially the tough ones. With CT,
dealing with life issues could be treated nearly the same way as solving problems in computer science.
Main Steps for CT...
Decomposing
As can be seen, de-composing, divide things into several small components while
facing a tricky problem, better for us to understand and absorb all the information of the issue,
greatly reduced the recognizing difficulty, in order to give corresponding resolutions
to each tiny problem more efficient and specific.
Recognizing features of an issue, find what feature dose the problems have in common, easily understand other same category issues.
Abstraction
Abandon useless information of a problem, especially the distracting ones, extract the key information and focus on it.
Algorithms
Basic logic of analyzing problems, usually
accompanied with conditional flowchart or pseudo code.
Generalization
Adjust/Optimize the model built to solve previous issues, in order to use it to deal with new problems in same type.
Necessities for future learning
CT is undoubtfully the key to make progress in daily learning. It greatly reduced
time spent on schoolwork and enhanced the quality. While doing programming assignment,
I'd first do a draft, to divide the project into a bunch of small problem waiting to be resolved. For each of those, I'd
ask myself some questions below...
Are there any IRRELEVANT information(if true, ignore them)...
What characteristic does the issue has...
Which category does the issue belongs to...
Did I develop project in that category before...
What function does it required to realize (especially the similar function that I've developed before)...
Is it proper to use the previous model for reference...
Additionally, I'd draw a conditional flowchart for each issue, to clarify what I've got to do in each step logically.
Ultimately, I'd start coding.
Career
Influences on my career will be significant as well. For instance, while working as a product manager,
I've got to develop several products, thus an overview for developing is required:
With decomposing, necessary steps of product developing has been listed, the objective become specific,
the fundamental logic become clearer. Besides,
model used before for developing product could be referenced to develop new project after being optimized.
In that case, large amount of time will be saved, so I can concentrate on researching new functions instead
of repeat developing same function over and over again.