100ProjectsOfCode VS CppCoreGuidelines

Work on a personal project. There's a list of 100 sample projects at https://github.com/arpit-omprakash/100ProjectsOfCode

https://github.com/aceking007/100ProjectsOfCode Pick an idea, attempt idea, google when stuck, probably do tutorial, finish tutorial, go beyond tutorial, profit. That’s a good way to start. If you have anything you’ve ever wanted to make then research. Go with any language really.

Grind leetcode and make projects. Have fun? Not anymore. For project ideas: https://github.com/aceking007/100ProjectsOfCode

100 Projects Of Code

With the basic languages done, move on to developing projects. The projects you create allow you to showcase the skills you have developed and serve as a proof-of-concept for the things you can achieve. Here is a great list of projects you can create to put on your resume: https://github.com/aceking007/100ProjectsOfCode

If you aren't aware of the c++ core guidelines[1] - it should be on your radar.

Also, it might not be a popular opinion, but I think Bjarne's books are just fine.

A Tour of C++ (3rd edition) [2]

Principles and Practice Using C++ (3rd Edition) was just published in april 2023 [3]

[1] https://github.com/isocpp/CppCoreGuidelines/blob/master/CppC...

You need to talk to Bjarne and Herb...

"C++ Core Guidelines" - https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines

In addition to the other comments -

TypeScript deliberately takes a "good enough" approach to improving JavaScript, instead of designing an ideal but incompatible approach. For example, its handling of [function parameter bivariance](https://www.typescriptlang.org/docs/handbook/type-compatibil...) is unsound but works much better with the existing JavaScript ecosystem. By contrast, a more academic functional programming language would guarantee a sound type system but would be a huge shift from JavaScript.

By analogy, Herb Sutter is arguing that something like the [C++ Core Guidelines](https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines), with tooling help in this new Cpp2 syntax, can bring real improvements to safety. Something like Rust's borrow checker would bring much stricter guarantees, backed by academic research and careful design, but would be incompatible and a huge adjustment.

https://www.youtube.com/watch?v=2olsGf6JIkU

Take a look at Effective Modern c++ by Scott Meyers and the ISO c++ core guidelines. These resources are great for learning how to write better, more modern C++. I don't think it would be hard to grasp if you're already familiar with the language, just make sure to actually write some code which makes use of this stuff, otherwise it's easy to forget.

Look to the C++ Core Guidelines. It's not perfect, it has some flaws, including some sabotaging advice apparently adopted for political reasons. But at least it has some C++ authorities (Bjarne and Herb) as authors.