there's not any major advantage in learning pure C unless you know for a fact you'll be working in a career that forbids C++ for some reason, usually a huge older C codebase with no plan for rework. you'll learn all of C while learning C++. the only thing you won't learn is some C-only ways of doing things that are the original ways of doing things before C++ STL, such as gnu data structures, heavier dependence on raw malloc calls, etc. and this is coming from a lifelong C programmer and C professor. learn C++. it's fine to start with C if you want, but transition into classes and templates and STL quickly unless this is literally your first language, which is seems it's not. More on reddit.com

I actually quite like the idea of your channel. That being I think you still have much too learn :-) First of all I think you should set up a github where you post your solutions, to make them easier accessible. My second point is - stop using macros! Please don't use them at all. There are lots of valid use cases for macros, but #define FORI(s,n) for(int i = s; i < n; ++i) is among the worst kind of macro usage (imho). If you use macros for stuff like this, I first have to learn your user defined macro language in order to understand your code. Besides readability there are tons of other arguments against macros (e.g. conflicting names when you include other files, potentially longer compile times, ...). My third point is that you should really stop using using namespace std; See also https://stackoverflow.com/questions/1452721/why-is-using-namespace-std-considered-bad-practice I furthermore think you could also show solutions which are using the std algorithms (as an alternative): int numJewelsInStone(const std::string& J, const std::string& S) { const std::unordered_set jewels(begin(J), end(J)); return std::count_if(begin(S), end(S), [&jewels](const char& c) { return jewels.find(c) != end(jewels); }); } EDIT: changed to count to count_if More on reddit.com

Very entertaining - one tiny quibble: The latter point is referred as the Small String Optimization and it means that short strings (generally 15/22 chars) do not go to the heap, but instead they get allocated on the stack This isn't quite true. In the SSO, short strings are stored in the std::string itself and don't require a separate allocation. However, the std::string might live on the stack or it might live in the heap, depending on how it was allocated. More on reddit.com

Vim with the right configuration is definitely the way to go for C and C++ in my opinion. In addition to cscope and YouCompleteMe, also learn about Vim's ctags integration which allows you to instantly jump to a definition under the cursor of a user defined type, variable, function name etc. Also, vim-dispatch is an easy way to build projects from Vim and works well with tmux. Tagslist is a nice plugin which opens a window that lists functions, classes, global vars etc. defined in the current buffer. More on reddit.com