diff options
| author | s1n <[email protected]> | 2019-08-16 02:53:26 -0700 |
|---|---|---|
| committer | GitHub <[email protected]> | 2019-08-16 02:53:26 -0700 |
| commit | a3f1b042619f891bb9e57bc162999a7f6ed68a95 (patch) | |
| tree | f200983cd9e2c55bf1e646ae5a5bd2afa6657032 /README.md | |
| parent | images (diff) | |
| download | cpp-terminology-a3f1b042619f891bb9e57bc162999a7f6ed68a95.tar.xz cpp-terminology-a3f1b042619f891bb9e57bc162999a7f6ed68a95.zip | |
add img
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 2 |
1 files changed, 2 insertions, 0 deletions
@@ -1,5 +1,7 @@ If you come from a web development background, and ended up learning C++ for some fortunate reason you must have ended up at this point at some point of time. Now if you are like most authentic coders, you must have started digging to see what experienced coders do to structure their code. Ironically even though C++ is really old and mature, the docs that are available out there are not very appealing to the current generation of coders who have been reading web framework docs which are easy to understand and follow. I don’t know why people have not taken such an initiative for C++. But truth be told, it is **not an easy language to learn.** + + In the web, these kind of tasks are usually automated. Third party libraries are also managed and added/removed by package managers ( Something that the C++ ecosystem lacks ). This gives you an opportunity to take full control of your project, and best of all, learn how things work under the hood. I will try to keep things as detailed as possible. There are two things C++ coders are concerned with while working on a massive project — 1. Maintaining a project structure |