Post by account_disabled on Mar 12, 2024 0:37:11 GMT -6
Keigo Meguro: Web engineer. In 2012, he entered the University of South Florida in Florida, USA. He is a computer science major. He will study a wide range of fields from web applications to system security and AI. He graduated from the university in 2016 and returned to Japan in March of the following year. He joined GIG in May. This time, he shares with us the lessons he learned from Dustin Boswell and Trevor Foucher's book, Readable Code, on how to write beautiful code. You can view the study session slides here. Readable code from GIG inc. On this day, many GIG members gathered after the scheduled time. Readable code is code that is easy for anyone to read.
"Code needs to be written beautifully so that when someone on your team or even yourself looks at it months later, they can instantly understand it, make changes, and find bugs." This idea was taught to me by Yoshi. Many engineers have heard this story. This idea is so pervasive Chinese Student Phone Number List that it is said that "engineers with dirty code are no good!", but not all engineers are able to embody this idea. So, specifically, how do you write to make it easier to read? ``Readable Code'' explains this . I'm not an engineer, so I can't understand difficult codes, but the one story that made me think, ``Hmm...'' was that the name I gave it was ``ambiguous.'' Let's use the analogy of moving.
I wrote the names of the main items on the cardboard box that was packed tightly, but there were actually a lot of other small items inside, and when I opened the package, I had no idea what was inside. I wonder if many people have had such an experience? For example, if you want to create a variable that means "column article", let's say you write "$column = xxxxxx;". The word "column" not only has the meaning of "column" of an article, but also has the meaning of "column (vertical column)". There was also a scene where director Kagawa-san asked a question. The content of this study session was also aimed at engineers, but the article content explains how organizing and recording information will make it harder to make mistakes and save you the trouble of reading it when you need to make corrections.
"Code needs to be written beautifully so that when someone on your team or even yourself looks at it months later, they can instantly understand it, make changes, and find bugs." This idea was taught to me by Yoshi. Many engineers have heard this story. This idea is so pervasive Chinese Student Phone Number List that it is said that "engineers with dirty code are no good!", but not all engineers are able to embody this idea. So, specifically, how do you write to make it easier to read? ``Readable Code'' explains this . I'm not an engineer, so I can't understand difficult codes, but the one story that made me think, ``Hmm...'' was that the name I gave it was ``ambiguous.'' Let's use the analogy of moving.
I wrote the names of the main items on the cardboard box that was packed tightly, but there were actually a lot of other small items inside, and when I opened the package, I had no idea what was inside. I wonder if many people have had such an experience? For example, if you want to create a variable that means "column article", let's say you write "$column = xxxxxx;". The word "column" not only has the meaning of "column" of an article, but also has the meaning of "column (vertical column)". There was also a scene where director Kagawa-san asked a question. The content of this study session was also aimed at engineers, but the article content explains how organizing and recording information will make it harder to make mistakes and save you the trouble of reading it when you need to make corrections.