C++ 학습하기: 기간 및 복잡성 인사이트

### C++ 배우기: 시간과 이해의 여정
* ⏳ C++를 배우는 데 걸리는 시간은 **기존 프로그래밍 지식과 달성하고자 하는 목표**에 따라 크게 달라집니다.
* 📚 숙련된 프로그래머라면 주말에 **'The C++ Tour'를 읽으면 탄탄한 기초**를 다질 수 있지만, 더 깊이 이해하려면 **며칠 또는 몇 주에 걸쳐 실험하고 라이브러리를 학습**해야 합니다.
* 🕰 반대로 링크된 목록이나 해시테이블과 같은 프로그래밍 개념에 익숙하지 않은 초보자의 경우, **전문가 수준에 도달하기까지 몇 달 또는 몇 년**이 걸릴 수도 있습니다.
* 🎻 악기를 배우는 것에 비유한 것은 **기본 기술은 금방 익힐 수 있지만 숙달하려면 수년간의 연습과 헌신**이 필요하다는 점을 강조합니다.
* 🔍 복잡한 로깅 클래스를 디버깅하는 경험에서 알 수 있듯이 **다른 사람의 복잡한 C++ 코드를 이해하는 것**은, 특히 수년간 코딩을 해온 사람이라면 상당한 어려움을 겪을 수 있습니다.
* 매크로와 템플릿을 비롯한 많은 기능으로 인해 혼란과 복잡성을 야기할 수 있는 **C++를 숙달하기 위해서는 고군분투**해야 합니다.
* 🛠 프로그래밍 언어를 안다는 것은 **구문을 넘어 그 언어의 용도를 이해**하고 기능을 효과적으로 적용하는 것까지 포함하며, 이를 파악하는 데는 상당한 시간이 걸릴 수 있습니다.
* 🌐 C++, JavaScript, Rust와 같은 언어의 다양한 접근 방식은 혼란을 야기할 수 있는 반면, **Go와 같은 단순한 언어는 단순함의 아름다움을 강조**하며 보다 직관적인 경로를 제공합니다.

숙련된 프로그래머는 몇 주가 걸리지만 초보자는 복잡한 C++를 익히는 데 몇 달 또는 몇 년이 걸릴 수 있습니다.

the founder of C++ on how long it takes to learn a language. The man who created potentially the second hardest modern - I mean the word 'modern' is loose here - but uh, you used language okay, because I understand there's like Malbolge and

BrainFuck which are arguably much, much harder, but this is not it. Okay, Rust being the hardest language then comes this: how long, how long does it take to learn C++? Depends what you want to do and what you already know. Um, if you are already a programmer

in quite a few languages, okay, um my recommendation is to read The C++ Tour, Tour of C++, great book by the way. I read it, very, very fantastic. I actually liked it. It uh, the, the description of how elegant the standard is and how it's

definition of iterators and everything was, it was seems so amazing, and then when you use iterators they're really awful in the standard. It's so, so much just typing. Just why do I got to type so much? But I love the idea of it, okay. I

love the fact that you can delete from one, it from a starting point to an ending point. It's beautiful. There's a lot of really great things in it. In addition, you can do it in the weekend, and now you have the fundamentals, and you have to do some experimentation and

probably dig deeper into the areas you're interested in. If you want to do anything, you have to pick up some libraries and learn them, but we're talking days or weeks. But that assumes you're a programmer. If I have to explain to you what a linked list is or what a

vector is or what a hashtable is, uh, then it takes much longer. So if you start from the beginning to reach the professional level, we're talking months and years. Um, and and and one question sometimes asked is how long does it take to learn to play a violin?

Well, if nobody's listening, it's easy. If only your mother has to appreciate it, uh, maybe it'll do fine. Um, but otherwise, it'll take years. Now if you're already a violinist and you want to play a viola, you can probably do it in a couple of weeks.

Depends what you are, uh, what your background is, what you already know, and then how good do you want to be at it. If if you're if you're thinking about the Lincoln Center, you better spend years. And I feel like learning C++ with prior

knowledge, he's probably right. It probably just takes a couple of weeks, a weekend, and all that. But learning to read someone else's C++ in which they've been writing for like a decade, it's going to take a long, long time. Okay, I remember being okay at C++

meaning that I can mostly do all the things in it, and I was I was pretty okay. This is when I was doing a lot of active development in it. Just a couple years back, I was doing a whole bunch and I I felt pretty happy about it. And then I go

to look at this logging class that was set up, and I spent three days debugging through the logging class. GDB print F, I even got C Lion out to try to help me on this thing. Never understood it. Literally spent about 40 hours looking

at code and never figured out how it works. Could I, couldn't I, couldn't I just... I don't know what voodoo magic I was missing, but this, this, this dance between macros and then code, then that the code then enacts more macros underneath like

that, that dance is impossible. When you get macros, templates, and code together, it's going to take you a long time, long, long time. The equivalent for, uh, a programming language, if you want to be the ace programmer, uh, building the next generation infrastructure, or the next, uh

absolutely great, um, oh, there's a lot of inheritance, too. Application, you better spend some years learning, not just the programming language, but your basic computer science and your application areas. I think one thing that he doesn't quite talk a lot about in this, I know

it's a very really short video, but some, something that he doesn't address a lot of is that it's one thing to know the language and what does it mean to know the language? Like, you can use what X percentage of its features? 70 percent of the features, 80% of the features

without like, you can kind of recall them and basically use them, but what does it mean to actually know a language? There's also kind of like a Zeitgeist or an intended usage of a language, and that intended usage takes a while to become like, to really get. Just because you

understand how to write the language does not mean you actually know the language at all. Just because I could write, say, lines of JavaScript, doesn't mean I am a JavaScript programmer. Even if you can write entire applications in JavaScript, you may not actually know how to use it correctly.

and it's also really hard to know how to use a language correctly, that you can do it in many different ways. And so C++, JavaScript, and Rust all suffer from this exact same problem, which is that there's like tons of different ways to solve the

exact same problem. And I find that to be a really difficult language to truly understand because as time goes forward, you could go into someone else's project as an expert and be completely just befuddled by it by how they chose to program it. It's massively different than how you

would do it and it becomes just like, it can become a very confusing thing. So many ways to do stuff, heavy abstraction, easy to do that. And JavaScript has the same thing. The only difference is JavaScript abstractions are often runtime abstractions as opposed to compile-time

and so it's very difficult. That's one reason why I've been really just appreciating this Go journey is that the Go journey, there's just really kind of like two ways you can do it, and it's beautiful. The name is, I'm in my

simplicity, Grug brain Renaissance, and I've been loving it.

Creator Of C++ On How Long To Learn A Language | Prime Reacts

This is a place for all the things that are awesome on stream. 

ThePrimeTime

C++를 배울 시간입니다: 이전 프로그래밍 경험에 따라 다름

숙련된 프로그래머라면 주말이나 몇 주 정도면 'C++ 투어'와 같은 리소스를 통해 기본 사항을 파악하는 데 충분할 수 있습니다.

초보자가 전문가 수준에 도달하려면 몇 달 또는 몇 년이라는 훨씬 더 많은 시간이 필요합니다.

학습 곡선은 악기를 배우는 것과 비교되는데, 사전 지식이 있으면 학습 시간이 크게 단축됩니다.

기존 C++ 코드, 특히 복잡한 프로젝트를 이해하는 데는 상당한 시간이 걸릴 수 있습니다.

숙련된 프로그래머도 복잡한 C++ 코드베이스를 디버깅하는 데 어려움을 겪을 수 있으며, 단일 클래스에 상당한 시간을 소비할 수 있습니다.

매크로, 템플릿, 코드 간의 상호 작용으로 인해 코드 로직을 이해하는 것이 매우 어려울 수 있습니다.

C++를 마스터하려면 언어 자체뿐만 아니라 컴퓨터 과학의 기초와 애플리케이션 영역에 대한 수년간의 학습이 필요합니다.

프로그래밍 언어에 대한 피상적인 지식 대비 깊이 있는 이해도

언어를 이해한다는 것은 그 언어의 특징과 사용법을 상당 부분 이해하는 것을 의미합니다.

단순히 코드를 작성하는 것만으로는 언어를 마스터하는 것과 같지 않으며, 언어의 사용 목적과 모범 사례를 이해하는 것이 중요합니다.

많은 언어가 동일한 문제에 대해 여러 가지 해결책을 허용하기 때문에 올바른 사용법을 판단하기 어렵습니다.

C++의 다양한 코딩 스타일을 이해하는 데 따르는 어려움

C++에서 문제를 해결하는 다양한 방법은 매우 다양한 코딩 스타일로 이어져 익숙하지 않은 프로젝트에서 작업할 때 혼란을 야기합니다.

C++의 과도한 추상화는 다양한 코딩 접근 방식을 이해하는 것을 더욱 복잡하게 만들 수 있습니다.

이는 바둑과 같이 접근 방식이 제한적이어서 이해가 단순한 언어와는 대조적입니다.