readable_code:: C++ development environment setup A to Z that is complete if you follow along

readable_code

cpp: Setting up the core development environment - A to Z of setting up the C++ development environment that you can follow along with.

Learn how to set up the essential development environment required for C++ development!

• I want to develop in C++, but... the environment settings are too complicated, right?

• I searched the internet to see if there was any information gathered in one place, but it was different here and there...

• In this course, I will teach you everything you need to know about C++ development, based on my extensive experience in the field!

  
  

Learn about these things

How to set up Git for source code version control

• I tried using GitHub once and I was surprised at how many things there were to set up...

• Set Github-related permissions all at once through the CLI!

How to set up a C++ development environment for various operating systems

• I tried to develop in C++, but it was different on Windows and different on Ubuntu...

• We'll show you how to set up a development environment that works regardless of OS!

What can you get?

• How to set up a C++ development environment regardless of OS (MacOS/Ubuntu)

• How to set up a Version Control System (VSC, Github)

• How to set coding fonts to improve development efficiency

• How to set up an Integrated Development Environment (IDE, Visual Studio Code) for C++ development

• Automating development environment setup through scripts

Keywords

• Development Environment

• Compiler

• Build System

• Version Control System

• IDE

• Coding Font

• Automation Script

Things to note before taking the course

readable_code

Why readable_code?

I still remember the feeling of self-doubt I felt when I first entered my graduate school lab and looked at the source code. "Ah... why can't I understand it no matter how much I look at it?" At the time, I thought it was my own shortcomings. More than ten years have passed since then. Now, I realize: the problem wasn't me, it was the code.

Many developers write code, cryptic, and cry out, "I have to get back to it!" But those codes soon come back to haunt them like a shackle. Code written without adherence to conventions for quick implementation and overused comments create confusion when reading, and carelessly created interfaces eventually make it difficult to discern what data is being exchanged. Code written this way, over time, produces incorrect results, becoming unreadable to anyone. Even the author of the code , after a week without looking at it, finds himself having to open the codebook called "Debugging" and decipher the code .

We call source code a language . Language exists to communicate with something. Many people mistakenly think that something is a computer. This misconception is why so many codes, called "codes," are created. (Isn't it interesting that code actually means "code?") However, as I mentioned earlier, code isn't something computers read, it's something we read. Therefore, writing source code is akin to writing. It's similar to writing technical documentation. We need to write code concisely and clearly, so that people can understand it. Code written this way is easy for anyone to read and understand. Unfortunately, in the field I've worked in, people often say they don't have time to consider and implement such trivial details. However, what I've learned is that it's not about "not being able to do something because we don't have time," but rather "not being able to do it because we can't."

Code that's easy for people to read ( readable_code ) is also easy for computers to read in most cases. This is because it doesn't implement unnecessary variables, functions, transformations, and processes. It also dramatically improves collaboration and code maintenance performance. For example, at my company, I abandoned the existing framework and designed and implemented a new one. This shortened code integration work that would have taken two weeks with the existing framework to just three days . Furthermore, module implementation, which would have taken three months with the existing framework, became possible in less than a month . The problem with human-readable code is that it's not something you can implement; if you can, there's no reason not to. It's an incredible thing that can dramatically improve development efficiency.

A mature development culture, collaboration, and readable code are often considered nice-to-haves, or rather, not essential. However, I've witnessed the power of readable code and experienced its practical application. While I can apply this knowledge locally to my company and team, I don't want to be satisfied with that. I want to increase Korea's software productivity. I want engineers to develop in a better environment. I want a good development culture to take root within Korean companies. From now on, I will share with you my experiences, successes and failures, and all the know-how I've learned along the way . These are invaluable and will serve as a solid foundation for your future path. Would you like to join us? (y/n) … -y