{"id":39,"date":"2016-02-20T06:35:36","date_gmt":"2016-02-20T06:35:36","guid":{"rendered":"http:\/\/lennycheng.com\/blog\/?p=39"},"modified":"2017-01-04T06:38:02","modified_gmt":"2017-01-04T06:38:02","slug":"similarities-between-english-and-programming","status":"publish","type":"post","link":"http:\/\/lennycheng.com\/blog\/2016\/02\/20\/similarities-between-english-and-programming\/","title":{"rendered":"Similarities between English and Programming"},"content":{"rendered":"

I recently attended an English lecture about writing good English. While listening to the professor, I suddenly realized that some strategies for writing good English also applies to writing good code! I don\u2019t profess to be an excellent coder yet (feel free to critique my projects on Github<\/a>) but I think learning techniques for writing scalable code and seeing the relationships between programming and other topics will help one quicker developer one\u2019s coding skills.<\/span><\/p>\n

Structure<\/h2>\n

Each book contains at least an index, dedication, conclusion, and main content. The content for some books are divided into sections, which may contain chapters, which may be further divided into headings and subheadings. Code also has structure. There are various files and subfiles, each with a clear focus. One files can be dedicated for updating the database; another file for keeping track of the state of the program; and another file for storing a list of every other file in the program!<\/span><\/p>\n

\u00a0Configuration files are the index pages; constructors are the opening paragraphs where we define our terms; destructors are the closing paragraphs where we wrap up the ideas we had communicated; comments are explanations of complicated content.<\/span><\/p>\n

\u00a0In essays and books, we often organize similar ideas under an overarching category instead of viewing them in solo silos. For example, \u201cReptilian digestion system\u201d, \u201cMammalian digestive system\u201d, and \u201cAmphibian digestive system\u201d can be grouped in a section called \u201cAnimal digestive systems\u201d. As a result, we help readers who read \u201cAnimal digestive systems\u201d understand the relationship between various digestive systems and how they are similar to each other instead of portraying each as an independent topic. In programming, we also group similar ideas together. We can place similar blocks of code in overloaded functions, use abstractions to represent concepts, such as creating the classes ReptilianDigestiveSystem, MammalianDigestiveSystem, and AmphibianDigestiveSystem to inherit from the class AnimalDigestiveSystem, or create projects that complete similar tasks. Grouping similar code together increases the maintainability of the program because developers can more quickly understand the purpose of and relationships between various chunks of code.<\/span><\/p>\n

Implementation<\/h2>\n
<\/div>\n
\n
<\/div>\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
Software and Life<\/span><\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n
\n
\n
\n
\n

Similarities between English and Programming<\/em><\/strong><\/h1>\n<\/div>\n<\/div>\n<\/div>\n
<\/div>\n
\n
\n
\n
\n

February 20, 2016<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n

<\/div>\n
<\/div>\n
\n
\n
\n
\n
\n
\n
\n
<\/div>\n

\"\"<\/div>\n<\/div>\n<\/div>\n<\/div>\n

\u00a0<\/span><\/p>\n

I recently attended an English lecture about writing good English. While listening to the professor, I suddenly realized that some strategies for writing good English also applies to writing good code! I don\u2019t profess to be an excellent coder yet (feel free to critique my projects on Github<\/a>) but I think learning techniques for writing scalable code and seeing the relationships between programming and other topics will help one quicker developer one\u2019s coding skills.<\/span><\/p>\n

\u00a0<\/span><\/p>\n

Structure<\/span><\/p>\n

\u00a0<\/span><\/p>\n

Each book contains at least an index, dedication, conclusion, and main content. The content for some books are divided into sections, which may contain chapters, which may be further divided into headings and subheadings. Code also has structure. There are various files and subfiles, each with a clear focus. One files can be dedicated for updating the database; another file for keeping track of the state of the program; and another file for storing a list of every other file in the program!<\/span><\/p>\n

\u00a0<\/span><\/p>\n

Configuration files are the index pages; constructors are the opening paragraphs where we define our terms; destructors are the closing paragraphs where we wrap up the ideas we had communicated; comments are explanations of complicated content.<\/span><\/p>\n

\u00a0<\/span><\/p>\n

In essays and books, we often organize similar ideas under an overarching category instead of viewing them in solo silos. For example, \u201cReptilian digestion system\u201d, \u201cMammalian digestive system\u201d, and \u201cAmphibian digestive system\u201d can be grouped in a section called \u201cAnimal digestive systems\u201d. As a result, we help readers who read \u201cAnimal digestive systems\u201d understand the relationship between various digestive systems and how they are similar to each other instead of portraying each as an independent topic. In programming, we also group similar ideas together. We can place similar blocks of code in overloaded functions, use abstractions to represent concepts, such as creating the classes ReptilianDigestiveSystem, MammalianDigestiveSystem, and AmphibianDigestiveSystem to inherit from the class AnimalDigestiveSystem, or create projects that complete similar tasks. Grouping similar code together increases the maintainability of the program because developers can more quickly understand the purpose of and relationships between various chunks of code.<\/span><\/p>\n

\u00a0<\/span><\/p>\n

Implementation<\/span><\/p>\n

\u00a0<\/span><\/p>\n

Implementation is about how to write the contents of a task to achieve a desired effect or purpose. There are numerous ways to describe a piano\u2019s appearance. Do we begin by describing the contrasting colour of its keys or do we begin by describing its contour and shape? Do we seek to emphasize the piano\u2019s size or texture? How sophisticated is our vocabulary for describing the piano? How do we structure our paragraphs such that readers see and feel the piano as vividly as we do?<\/span><\/p>\n

\u00a0There are also numerous ways to sort a list of elements. Shall we apply merge sort or quick sort? Is our goal to achieve faster time or less memory usage? To use or not to use design patterns? Do we use multithreading to or does a single thread already suffice our needs?<\/span><\/p>\n

\u00a0In both writing English and coding, we thoughtfully express our ideas and implement our designs by contemplating about the final result and then welding our mastery of syntax, semantics, and other language subtleties to achieve that result.<\/span><\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

I recently attended an English lecture about writing good English. While listening to the professor, I suddenly realized that some strategies for writing good English also applies to writing good…<\/p>\n","protected":false},"author":1,"featured_media":40,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[5],"tags":[],"_links":{"self":[{"href":"http:\/\/lennycheng.com\/blog\/wp-json\/wp\/v2\/posts\/39"}],"collection":[{"href":"http:\/\/lennycheng.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/lennycheng.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/lennycheng.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/lennycheng.com\/blog\/wp-json\/wp\/v2\/comments?post=39"}],"version-history":[{"count":2,"href":"http:\/\/lennycheng.com\/blog\/wp-json\/wp\/v2\/posts\/39\/revisions"}],"predecessor-version":[{"id":42,"href":"http:\/\/lennycheng.com\/blog\/wp-json\/wp\/v2\/posts\/39\/revisions\/42"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/lennycheng.com\/blog\/wp-json\/wp\/v2\/media\/40"}],"wp:attachment":[{"href":"http:\/\/lennycheng.com\/blog\/wp-json\/wp\/v2\/media?parent=39"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/lennycheng.com\/blog\/wp-json\/wp\/v2\/categories?post=39"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/lennycheng.com\/blog\/wp-json\/wp\/v2\/tags?post=39"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}