{"id":5983,"date":"2017-03-27T09:00:52","date_gmt":"2017-03-27T02:00:52","guid":{"rendered":"https:\/\/stei.itb.ac.id\/?p=5983"},"modified":"2017-04-04T11:45:01","modified_gmt":"2017-04-04T04:45:01","slug":"kuliah-tamu-teknik-informatika-itb-kunci-pemrograman-sukses-dengan-clean-code","status":"publish","type":"post","link":"https:\/\/stei.itb.ac.id\/en\/kuliah-tamu-teknik-informatika-itb-kunci-pemrograman-sukses-dengan-clean-code\/","title":{"rendered":"ITB Informatics Engineering Guest Lecture: The Key to Successful Programming with Clean Code"},"content":{"rendered":"
\n

\"\"<\/a><\/p>\n

BANDUNG, itb.ac.id \u2013 Nearly all companies today use software and computerized systems to automate the resolution of various problems. Unlike building construction or other common tasks, these systems are built using programming algorithms, databases, and designs that are not tangible. When a company wants to expand and develop, the systems that support it must also develop and maintain them. To achieve this, the programming of these systems must be carried out step by step in a gradual and clear manner. One important foundation in building a system is writing code in accordance with applicable standards and conventions. To meet this need, the Informatics Engineering Study Program invited GDP Labs to host a lecture entitled \"Clean Code<\/i>\u201d on Friday (24\/03\/17) at 14.00-16.00 in room 9009 LFM, Bandung Institute of Technology.<\/p>\n

Glance at Clean Code\u00a0<\/b><\/div>\n
Clean Code<\/i> It's a recognized practice in coding, including writing variables, methods, and classes, as well as error handling. While it may seem insignificant, poorly written code has been proven to destroy projects and companies.<\/div>\n
Hukum LeBlanc menyatakan bahwa \u201clate equals never<\/i>\", namely rearrangement bad code<\/i> Late projects will never materialize. This results in code clutter and makes it difficult to add features to the system. Companies will spend a lot of time and money supporting code maintenance and may end up going bankrupt. By implementing Clean Code<\/i> From an early stage, companies can focus more on adding new features and system updates to develop themselves, rather than maintaining legacy code.<\/div>\n
<\/div>\n
Naming variables, functions, and classes\u00a0<\/b><\/div>\n
The names used for variables should reflect what the code does, why it was created, and how it works. Good, unique naming also reveals the intent of the programmer who wrote the code and makes it easier to find variables within a program, making them understandable to others who continue developing the program or system. GDP Labs also emphasizes that each function should be small and fulfill only one purpose: either to do something or to provide an answer to a problem, but not both.<\/div>\n
Furthermore, GDP Labs also urges to avoid excessive parameter usage in functions. In object-oriented programming, classes are used to provide attributes and implement behavior for an object. To write clean code, programmers must also pay attention to the order in which a class is declared. GDP Labs also reminds us that each class should be small, have only one responsibility, and each method within it should be highly cohesive.<\/div>\n
<\/div>\n
Pemberian Komentar, Formatting<\/i>, and others<\/b><\/div>\n
There are several things to consider when writing code, one of which is commenting. Comments are parts of a program that aren't executed, as their function is to explain the code so that programmers reading it can understand it. The best explanation for a block of code should be the code itself. Clean Code<\/i> teaches how to improve code readability, eliminating the need for comments. Comments should be informative, explaining the programmer's intent, and reminding the programmer of the consequences of using that block of code.<\/div>\n
Another important thing to note is formatting<\/i>, namely how to place functions, classes and variables according to standards, as well as indentation and alignment <\/i>GDP Labs also briefly discusses proper error handling and why code rebuilding is necessary.<\/div>\n<\/div>\n
<\/div>\n
Via\u00a0ITB.ac.id<\/a><\/div>","protected":false},"excerpt":{"rendered":"

BANDUNG, itb.ac.id \u2013 Hampir semua perusahaan dewasa ini telah melibatkan perangkat lunak dan sistem-sistem yang telah terkomputerisasi untuk mengotomasi penyelesaian dari berbagai persoalan. Berbeda dengan konstruksi bangunan atau hal lain […]<\/p>\n","protected":false},"author":1,"featured_media":5984,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[250],"tags":[333,337,339,73,54,335],"class_list":["post-5983","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-acara","tag-clean-code","tag-coding","tag-kuliah-tamu","tag-kuliah-umum","tag-programming","tag-teknik-informatika"],"_links":{"self":[{"href":"https:\/\/stei.itb.ac.id\/en\/wp-json\/wp\/v2\/posts\/5983","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/stei.itb.ac.id\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/stei.itb.ac.id\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/stei.itb.ac.id\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/stei.itb.ac.id\/en\/wp-json\/wp\/v2\/comments?post=5983"}],"version-history":[{"count":0,"href":"https:\/\/stei.itb.ac.id\/en\/wp-json\/wp\/v2\/posts\/5983\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/stei.itb.ac.id\/en\/wp-json\/wp\/v2\/media\/5984"}],"wp:attachment":[{"href":"https:\/\/stei.itb.ac.id\/en\/wp-json\/wp\/v2\/media?parent=5983"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/stei.itb.ac.id\/en\/wp-json\/wp\/v2\/categories?post=5983"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/stei.itb.ac.id\/en\/wp-json\/wp\/v2\/tags?post=5983"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}