You made this video just to get drama. No you should not learn C++. Lots of people know it, few companies use it, most are moving away from it, there are better languages if are starting a project. Anyone leaning C++ will only annoy experienced users. Like you said. The first language anyone should learn is python, then Rust or C, then TS or JS. Maybe Bun. Everyone can use Python because there is always some quick little task that you can get done with python in a few minutes that will make any computer users life better.

It depends on what your coding (I like c++)

C++ MUST DIE.

@@MichaelMantion That's wrong. C++ is still being used in industry and will never go away completely.

When I use C++, I program it like C, it is objectivly better.

Except for Java , both nobody uses it except for Indian tutorial makers and somehow everybody still hates it.

@@user-fr2fm3ri3w nah errybody use Java

@@user-fr2fm3ri3w java deserves its hate.

@@user-fr2fm3ri3w nobody uses it.... lol what field are you working in?

@@fr3dlopez it used to be good for cross platform and for android but it got murdered by kotlin and electron. Maybe it can still be used in a server but go and rust are flat out better. Companies that use Java still only do so because it’s too expensive to migrate, Java’s market share is falling each year however

words are hard. you right

Though C++ is not a strict superset of C, as it is not 100 % compatible with C. Depending on the standard of course, as the latest C and C++ standards try to move to a closer common ground again.

As is mentioned in the video, C++ is C with object, so doesn't that mean C++ is a subset of C?

@@retsu-h6460 If C++ was a subset of C, C++ code would be valid C code, which is not the case, it's the opposite. But as mentioned, it's not a 100% superset anymore since C99.

​@@theawesomefire: _"Though C++ is ... not 100 % compatible with C."_ I wish I could remember the issue, but years ago I went round and round with another developer because I gave him a few lines of simple C code that I compiled and tested with my C++ compiler. It worked flawlessly for me but he argued that it didn't work for him. When I finally tested it with a C compiler I found he was correct.

I wish I would have known that before spending years on low level programming before realizing most relevant jobs will require proficiency in another field

Exactly. and this is why I hate people who push others looking in from outside the industry to only learn a single language like python to start their journey. You gotta learn a lot of things first to narrow down what you wanna go into and then you dive deeply into its requirements.

It's mainly about which language to choose to learn for people that haven't started yet or haven't progressed very far. They'll be training themselves in both programming and the language they choose and that choice partly depends on what work might be available, what they want to do, and what is good at a learner level.

@@andrewdunbar828 shouldn't they choose a subject instead of a language?

@@sososo3906 They will choose many subjects. That's what everyone I knew did, though there were fewer languages to choose from then.

Should've just skipped to Rust.

The first 2 months learning Rust will be very painful, but it is probably going to become your favorite language.

@@sotam8938 Well rust isn't really good for jobs, C++ still and will forever have codebases to maintain. C++ isn't horrible the programmers abusing its concepts are thus resulting in its reputation for memory leaks, Try to use smart pointers and keep raw pointers as a last measure.

@@punchcake4832 At the end of the day, programming languages are tools, each with their pros and cons.

C++ is the building foundation of a lot of stuff in our world nowadays...

If you can learn c++ you can learn any other language lol

@@yurikadzz truth brother

okay, now do X86 assembly, must be easy now :P

@@Henry-sv3wv Assembly, especially x86 might unironically be simpler than C++ or even C atleast in terms of syntax. it's just more tedious, time consuming and requires a solid understanding of how the CPU registers and memory stack work.

@@user-xw4od8kb7y Bro, can you recommend any beginner-friendly literature (if such thing exists lol) on asm and cpu architecture?

I've had similar experience in my job. Unravelling my co-workers fancy and redundant code was a gruelling task.

what do you do as a embedded developer? sounds interesting

​@@XenolVlatriX: _"what do you do as a embedded developer?"_ Embedded computers are those with no user interface or a limited interface. The microcontroller in a microwave is the most familiar example. I worked with telephone switchgear, solar controllers and bus communication systems.

Terry davis once said the simple mind craves complexity or something like that.

Thank you. I work a few million lines of crap above you (web), fighting the complexity demon wherever it decides to come to nest. It's come to be point now where I find myself having discussions with senior engineers over the extreme danger of writing for loops in bounds-checking, memory managed languages, as 'you could get them wrong' and 'they are hard to read'. I would give someone elses arm to write Go on the frontend, anything but JavaScript.

agreed, im not a proffesional neither intermediate of the language but when you dedicate time to the language and actually understand the ins and outs its pretty awesome, the power we have also its a must for anyone wanting to get into malware analysis or Reverse engineering

I tried getting into c++ for a while (currently i use rust) but I'd say c++ more than any language requires you to just "know" things, or at least thats how it feels. Like solid code sometimes just wont work because theres some quirk of the language or compiler or something that just screws with specific implementations that seem like they should work. It feels like to bugfix you need to have a textbook just containing these irregularities of the language itself Also header files confuse me because im kinda dumb but thats just a c thing

I realize this is a month old, but could you by any chance expand a little bit on the idea of "raw pointers are ok so long as they're not owning pointers"?

@@user-sl6gn1ss8p Well, the thing is owning pointers are pointers which manage the lifetime of the object they are pointing to. That means that smart pointers in C++ are owning pointers because they have to destroy the thing they point to at the end of its lifetime. If A owns B, that means that A has to destroy B when the time comes. That means that Non-owning pointers do not manage the lifetime of the object they point to, they just "look" at the object. They don't have any obligation to the thing they point to. That is why raw pointers are "ok" to use in a non-owning scenario. They are great if your function requires a view to the object. Nothing is hindering you to use pointers as you wish, but abrstractions like these are really handy when you have to reason with code that you are unfamilliar with. The purpose of abstractions is to carry intent. I hope that I made it a bit clearer. :)

@@aleksandarnikolic2441 thanks, it does seem to make a lot of sense : )

range-for loop is just syntactic sugar equivalent to an iterator loop.

Yeah. I guess std::for_each(v.begin(), v.end(), []() {}); exists too, but I never understood why you would do that instead of ranged for.

@@danielsan901998 range-for loop also works on arrays. Furthermore, it doesn't matter that it is syntactic sugar over something. It matters that is a better syntax. Iterators suck because they are verbose and ugly.

@@sledgex9 it does matter that it is syntactic sugar because the point was "avoid sugar", and for-range loops is an example in favor of using syntactic sugar.

@@danielsan901998 IMO, I took it to mean "don't structure your code in a way just to make use of all c++ features". Notice the absence of std::vector in the second example. If I was wrong in my interpretation of his point, then I consider that point a wrong one. Using syntactic sugar that makes things easier to write/read and less bug prone (off-by-one error in for-loop), is a MUST. Otherwise we should avoid lambdas too because they too are syntactic sugar over special structs.

I recommend using smart pointers as much as you can. With those you can be in 99% of the cases sure that there won't be memory leaks

I’m somewhat of a masochist myself

@@xvxluka222 I do whenever I can, but sometimes raw pointers are better, when calling native OS functions

@@chicoern heads up: look for std::out_ptr, it's been invented to deal with OS calls that expect in-out raw pointers.

@@Tibor0991 oooooooh didn't knew that! Thanks buddy!

my dude🤣🤣

"tweeted" ?

@@victotronics yes

@@victotronics are you born now or what?

don't waste your wishes, because like a plant, you should water the best and cull the rest.

There are modern alternatives now tho, so no, it cannot be found in ALL projects where those things matter…

@@Stumashedpotatoes "uhm ackshually" yeah yeah shut up. It probably STILL can be found in all those projects but indirectly. Rust for example uses LLVM to be compiled and LLVM is programmed in C++.

@@sharoyveduchi my point was that you do not need to write CPP yourself to get the performance of C, by using rust or zig. Buddy you just did the biggest “um actually” I’ve ever seen. You brought up the fact that the compiler is written in cpp. “Umm akshually the compiler is written in cpp so youre still using it even when you’re not”. You gonna tell me Linux is written in C too? Cringe bro, cringe

@@sharoyveduchi Fair point but unnecessarily vitriolic, Stuarts remark was completely fair and nothing about it was offensive.

@@Stumashedpotatoes idiot. Every big electrical and mechanical CAD which used to build stuff we use in our life is coded in c++

Agreed, working on a project that stretches 4 platforms (windows, linux, microcontroller, embedded linux) and build systems are a pain to get right if you don't want to enforce usage of a specific IDE. CMake frustrated me to all hells with how most of the methods turn out to be "not recommended anymore" but then recommended methods for cross-platform use are lacking BIG TIME (especially how msbuild wants release+debug setup, I ended up dumping that), overall CMake was really unintuitive. NMake started fine (basically a simple syntax change from Make) but became a real drag once it got a little more complex with how badly it is supported. So I now use CMake for windows so I don't have to deal with manually maintaining msbuild project files, Make on Linux, Make for Microcontroller, and a simple CMake + SH for embedded linux. I dread the day something requires me to touch it again.

​@@vocassen have you tried premake its available for windows linux and mac?

also what i forgot to mention is that build system can be VERY complex in cpp. I don't have a lot of proffetional experience working with other languages but I don't think that in java or c# properly setting up build system can be so hard (even with cmake)

Good developers makes everything work fluently in any language 🙂 I understand what you mean with guidelines, but you also need some freedom to break the guidelines to find better ways. I see a lot of projects becoming hard to handle because of enforced guidelines. I think within the same project the code should be consistent. But between different projects the consistency can be different depending on the projects need.

Not using STL in 2022 is shooting yourself in the foot from the start; why avoid type and memory safe structures with zero memory and performance overhead?

@@olafbaeyens8955 of course i mean in single project single guildlines, as for flexibility in smaller project it should be fine, personally i work on 5g with hundreds other people so rules are enforce at ci level

@@Tibor0991 we just use boost ore have our own libery

For me, understanding RAII as a mechanism for letting the compiler safely manage your resource lifetimes was eye opening. It moved me away from this “code in C” style

I learned higher level languages first and C++ before recently learning C. I can tell you, for embedded systems, C is still much preferrable compared to Rust, especially when doing bare metal. C is almost married to embedded systems in a way other languages aren't. And personally, having now learned C, i think for complex systems, it can be a death trap, but it's simplicity also taught me how be efficient as a developer, especially with memory

@@juniorjunior8494 I do agree but that's why I specified that I'm talking about general use cases and not special ones like embedded.

@@4cps777 Even if this common belief of "C is better for embedded system" is completely false, they are tons of project in C++ and rust for embedded system. Arduino uses C++, ARM dev program libraries are in C++. C is used as a lingua franca so devices drivers are written in C so it can be used for every single languages, that’s all. Once you said that, nothing force you to use C as most languages can use C ABI.

But even drivers can use a C abi and under the hood be written in C++ or even rust.

If you're not using it for your job try rust and never look back

@@sososo3906 rust fanboys again ruining everybody days

@@KopieOG your right, finding out that the multi million dollar code base your company developed for 30 years will cost about as much to rewrite to be understood by anyone besides the original writers won't ruin your day, it will ruin your life

i use python for automation and c++ for making programs

@@hodayfa000h if the code is written from scratch you should write it with rust, also it easy to make a python library and only implement in rust the bottlenecks of python

No needed for C++ here. You could just get around with C which is much simpler and easier.

@@thecoolnewsguy hmm nah, unless you want to do embedded stuff

@@anon1963 I meant in terms of learning the fundamentals of memory management and programming not in terms of getting a job or building a software.

Have you tried Rust? The error messages from that compiler are consistently the most helpful I've ever seen.

@@0xTas I actually havent. I tried Go but not Rust. Thanks for the suggestion.

What's your job?:3c

There's no reason to use malloc in C++ instead of new. Sometimes you may want to dynamically allocate a class that has a constructor, in which case new is the only way to do it properly. And using two different constructs to allocate memory throughout your program just adds mental overhead, instead of reducing it

@@xGOKOPx I should've been more specific, I do use new most of the time

@@whamer100 This is why rust is the leading programming language.

@@myself50094 i should really learn rust tbh, the syntax annoyed me last time i tried it, but that was a couple years ago

@@whamer100 i'm a troll

I totally agree. I have the same feeling. I'd prefer be in control then to just have "trust me, bro" experience when I'm trying to worth with technology.

goto spaghetti is anathema to programming, drop down coupling is pure miscegenation of coding. DRY? if repeating is the root of all evil (silly uncle bob) then i am WET because virtual is infinite.

There’s no better language than C to understand how hardware works, that’s why I’ll also stick with C for embedded

I think C++ is going in the correct direction with safety. Though they will never get as far as Rust. The main things that still bug me when working on C++ is threads safety and lifetimes. Companies I have worked with have flat out ban threading because it just causes so many bugs in what needs to be a safe system. Lifetimes are just never explicit in C++ you just have to hope things are documented well. C++ is not bad but it has years of issues that cannot be fixed.

@@dynfoxx I think the threading issue is due to the not explicit (bad) lifetimes in c++. The first time I managed to get UB in an actual project was because some undocumented behavior in a library causing a pointer to that was required to become invalid. It took me days to figure it out because I checked if it was valid the line before I passed it. Multi threading itself is not that difficult, but using it efficiently usually means there are a lot of side-effects that become hard to keep track of. But if you have some expensive algorithm iterating over a lot of "uncoupled" data, it is not that hard.

@@someonespotatohmm9513 it's not that hard in theory. But when C++ gives you no help and it's up to documentation that may or may not be followed it gets to be a problem. The fact that programs don't know atomic, volatile and shared pointer safety just gets annoying. Half of the issue is that you can do it right but it's just hard to keep right. If I am not careful some other person will come mess it up. They need owning mutates like rust has. It makes it more clear to start with. Though it will never be fixed it more so comes down to your code base and fellow engineers.

Short overview of Modula 3 and Ada gives an idea that Rust solved the problem which was solved long time ago, just not in world of C-family languages. Yes, it needed few decades to catch up, but better ever than never.

Can you recommend the resources for c++ ;)

​@@hecker230 A good place to start would be a channel called "The Cherno", he offers a wide variety of C++ videos, but you will have to move on to other stuff later since he doesn't cover everything. I also recommend watching some C++ weekly videos from Jason Turner once you get more advanced. (I also recommend you learn C first) *Good luck!*

Cool, I started with Java in uni and then became interested in C# but I’ve always had books about and interest for C++ for it’s efficiency and industry impact. I also like learning about backend development with .NET and C#. I’m having a really hard time deciding which one of these, C++ or C# to learn! I’m interested in topics like graphics, backend web dev, but even then, I have a hard time deciding!

​​​@@erik9817 C++ is so important for your journey as a programmer. Even if you later learn a language unrelated to systems development, C++ gives you great insight into how to make more performant code. Other languages are also much easier after learning C++. Without learning pointers, for example, it can be harder to learn how all the objects connect together in C#. (C# has pointers called references, but they hide them). If you decide to go for a higher level language, try to not depend on a framework (like Unity) to learn the language. Otherwise you will be dependent on the framework and you won't learn how to structure the code on your own. C# is a really good language, but all programmers should learn C or C++ at some point imo to get a better understanding.

Nice comment! I feel that I have a hard time deciding between focusing on C++ and C#. I've spent some time learning C# but C++ has always been in the background, I was also intimidated at first, but I bought books about it several years ago.

I can relate to this. My mind needs to have a deep understanding of how things work. When computers were simpler, I understood them at hardware level. You also need a hardware level understanding to effectively program microcontrollers. C and C++ are "close to the machine" and just suit the way my brain works. It's hard to explain exactly what that means to someone who doesn't think that way, but I completely understand what you're saying.

How much salary ? And does it make permanent

You are set to go! Having done some coding in C and high level language is enough to get started!

IMO if you've properly messed around with memory and know how you can really mess up without being careful with memory, then you can try learning Rust, you'll then appreciate what it tries to solve. So you're good. Try learning it

You can definitely jump in as you are right now, I was only marginally familiar with Python and Javascript when I started learning Rust (like ~5 months ago) and it's already my most comfortable and also favorite language to work in! Start reading through the book and don't give up when things get confusing! Rust has some concepts like lifetime annotations which won't be familiar to almost anyone at first but if you can push past those and the other low-level concepts that are new to you then you'll have access to one of the most pleasant languages to use imo, considering what it can offer.

If you start out programming I would say rust because of the shooting yourself in the foot thing. If you are going to use it, whichever one best fits your purpose. The biggest difference between the 3 are the language features and syntax anyway.

Learning C will only hamper learning Rust. You can easily write in C++ as if it was C. If you try the same in Rust(and you will if you learn C first), borrow checker will crush you.

Totally agree. It's a good language that is VERY easy to use incorrectly.

It's like C++ wants to do it all and integrate all new languages into C++style, at the time the new languages were hyped.

What? STL is its strong suit. It is very powerful and useful. Just take a look at the module. And you pay for what you use from it.

PS.: The funny thing is, that all C++Conference talks got a strong Rust-flavor in 2022 xDDD

@@sledgex9 you are right but for embedded most stuff is bloated and MISRA discourage usage of std library

The latter isn’t a C++ issue though? It’s how that particular dev team decided to use other packages.

Last paragraph: Probably to abstract away the use of QColor.

the correct answer is neither

Do you know Rust?

I agree it's underrated. If I had to pick one language to be the most versatile, C++ is it. But it's terrible for some applications - web apps and data science for example.

We programmers suck at talking :D

Exactly, well said. People really taking away the low-level part and cry about the language because they come from languages like python and expect to breeze through it. C++ teaches you things you would never learn as a person who works only with very high-level languages, it really teaches you good programming practices, how the compiler works, OOP and just how to optimize your code

@@Dulge Thanks. Though I don't think C++ teaches good coding practices more than other languages either, or i didn't understand what you're saying. C# for example, does things differently but is pretty well structured. C++ is actually pretty relaxed in comparison to Rust. If people think C++ is hard then I do think C++ has problems in accessibility. I don't think it should be hard to use. C++ also has problems with usability. Eg. Static reflection...

@@noxagonal Yeah, i feel like the "hard" aspect is there for a reason however, if C++ was easy and we didn't need to do extra steps or have to understand pointers, references, OOP, virtual functions, inheritance, polymorphism and just a bunch of rules the language has then it wouldn't be powerful and used in nearly every engine, library or wherever programs and embedded systems need that performance and power

@@noxagonal As for the Rust being harder i personally would disagree, I think learning rust as a person familiar with another language makes it harder to learn then for a person who is brand new to programming because the way rust is. Mainly because of the legacy aspect C++ and most languages follow

@Dulge I probably shouldn't talk about Rust as I haven't used it on any actual project yet. I think we're approaching this from different perspectives. For example, if you try to use iterators in C++98 vs. C++20, you'll see what I mean. I think some basic knowledge about hardware is necessary in any compiled language, but even then, much of it could be abstracted in language level so that it still performs good. I think C++ could use a complete second standard library altogether, as complete as the current stl but without the history. Most game engines use stl minimally because it's ill suited for game development, though better nowadays, there are still many reasons to not use it. Easier, in this case, would be to have better utilities that we wouldn't need to write our own.

"C is what you get when you almost always say no to adding something to the language. C++ is what you get when you almost always say yes to adding something to the language "

@@MrWi1y and "Rust is what you get when you design a language sensibly from the start" :p

@@0xTas : Oh? Then why does it still use symbols to declare pointers? That was an _experiment_ when C did it, and it hasn't turned out to be a great idea.

@@0xTas Another Rust shill. How much you get paid per post?

Mind giving an example? I can’t think of something that actively hurts readability other than templates and SFINAE - the latter of which is getting replaced with concepts (an evolution, not a devolution).

Going down to C is too far imo. Now you have to deal with poor typing capability and memory management (mistakes).

@@climatechangedoesntbargain9140 If you're sufficiently self-disciplined with the code you write, these are surprisingly minor issues. With a healthy mix of assertions, automated testing, static analysis, defensive programming, shunning "clever" code and using a good debugger, I spent very little time and effort on debugging.

@@Spiderboydk but every time you will mess something up you will have to stop with the project and figure out the correct discipline instead of what you tried to do

@@sososo3906 I don't understand what you mean by "stopping with the project and figuring out the correct discipline". Are you talking about switching programming paradigmes?

@@Spiderboydk i mean that in c you have a bug and forget about whatever you were doing because now you learn debugging, in rust the only fear is that you will have to learn lifetimes

You described the same problem people have with Unreal Engine It just throws every single feature at you and makes it harder to learn, whilst Unity is a lot more simple to start learning

@@tuluppampam yeah the main issue is that idiomatic, modern c++ requires you to use use many advanced features of c++. In order to actually understand them it's best to learn old school C++ first and then move on to the modern features, because the necessity for modern c++ only becomes apparent when you understand the problem with old school c++. The issue I see here is that many people in the c++ community are quite toxic when it comes to newbies not using "the idiomatic way" of implementing something.

For me it's that none of the features seem to mesh well together. They all seem separated and still in a first revision state. It just feels unfinished for some reason.

It is not just about classes and objects. Todays C++ standard library provides many useful features such as algorithms, threading, file system and much, much more. You don't have to reinvent a wheel and it is really fast. Even memory allocations if done right, you dont need to worry about releasing memory. Though you need to know how templates work :)

Oh cool! I'm really intrigued by Nim. Do you know if it's being used professionally much, yet?

c++ isn't low level

@@phoneywheeze9959 compared to other languages these days id say it is

I still use C whenever I can even when I code in C++. Yes, cin and cout are nice, but printf and scanf allow more easier

@@BederikStorm Bro this is a joke, cuz if you do ++ it means + 1, i ain't arguing what's better lol

No real advantage, except declaring the variable inside the for loop scope wasn't valid C until C99

You don't have to use the unnecessary features and obscure things, but I guess the problem is when you have to work with code somebody else wrote.

Is it a good book to learn C++ from?

C++? Aesthetics? Come on bruh

@@bmno.4565 u gotta admit c++ looks pretty cool ngl

Good for you. I think it's great that you learn C++ rather than Python. IMO Python is bad as a first language because it gives you a bad intuition about data types, contrary to any statically-typed language, like C++. And if you ever feel overwhelmed by C++, you can always switch to C. Though, my recommendation would be the same as in this video: to first learn C (as it's just as sophisticated, but much simpler), and then move on to C++. But if C++ excites you more, go for it.

@@hottoniapalustris1541 same. I think personally that a language like Java or C++ is a great first language because you get to learn alot and be more involved in the code. Thus making your migration to other languages way more seamless. But thats me personally loving the trial by fire style of learning

If its working for you, it doesn't really matter. Whatever language you use, it just needs to be good enough to make the projects that will allow you to learn what you need, without being so frustrating so that you might lose motivation. I think python is a good stepping stone and I like it for quick proof of concept type things. Potentially, python lets you skip the syntax and focus on learning how to give computers instructions first... control flow and all that, but its also allowed me to adopt some bad habits, like overusing list comprehension to quickly define arrays in a sometimes unreadable fashion, though I'm sure there different sorts of bad habits you can pick up from different languages. There's also some cryptic errors in python, usually around how things are copied or passed around, which make a lot more sense when you know about pointers and references, after all python itself will be written in c.

It’s better to learn a language than get stuck deciding which one to learn first.

@@hottoniapalustris1541 Imo c++ is worse then python, you have some weird unintuitive stuff in python but when using common libraries like numpy most things will be effectively statically typed. With C or c++, gl debugging if the first problem you run into is UB, which it likely will be. And UB in your own code is not even that bad as presumably you have reasoned about and tested stuff. But then you use a library and it does something else then you expect, well good luck if it something like a collision checking algorithm.

@@kmouratidis If you do Python than C++, it's like climbing one storey of the stairs. Starting C++ is like trying to jump to the next storey with no stairs

@@LowestofheDead Disagree. There's more syntactic complexity but it's very possible to stay away from all the parts that actually make C++ difficult. If syntax is your blocker for learning programming, you have a tough road ahead.

If C is explained well it shouldn't be that hard to understand at least the basics.

@avfr hardly disagree. Excel in languages you actually need, try and learn other (maybe even obscure) languages to widen your horizon as a software developer.

@avfr You assume people can only do isosceles triangles and temperature converters after 1 month of C? Get off your high horse lol. Not everyone chooses C as their first language. If you've got plenty of experience in, let's say, Python and JS, it wouldn't even take a month to learn C, the standard library is not that big, especially compared to Python and JS. Doesn't mean you're suddenly being able to code kernels and stuff, you'll need way more knowledge than just C for that. It's like spoken languages. Just because you're proficient in English doesn't mean you'll be the next Shakespeare. Or the next Mozart if you can play the piano. _ As an anecdote: after seeing Haskell for the first time I immediately fell in love with it. Got myself a copy of "Learn you a Haskell for great good" and worked my way through that book in less than a month. Delightful read! I wasn't able to code anything I want at that point, but oh well, it's Haskell after all. Fiddled around with it for a couple of months and eventually stopped digging deeper. I'd say I'm pretty good at it now, though I only really use it to tackle and solve projecteuler problems, never used it for professional purposes. I can say with confidence that it boosted my abilities in Python(mostly data analysis and simulations, if we're talking about money making :)) like, A LOT, as well as my problem solving skills as a whole. It started as a recreational activity, for the jest of it, and now I'm a better programmer. Am I a Haskell god? No. Have I learned the whole language? No. Who cares? And who cares what and what not someone can do after 1 month of C?