Book-For-Programmers VS clean-code-typescript

https://github.com/jnguyen095/clean-code/blob/master/Clean.Code.A.Handbook.of.Agile.Software.Craftsmanship.pdf https://github.com/forkarea/book/blob/master/M.Fowler%20et%20al%20-%20Refactoring%20-%20Improving%20the%20Design%20of%20Existing.pdf https://github.com/minhloc2011/books/blob/master/Don't%20Make%20Me%20Think%20-%20A%20Common%20Sense%20Approach%20To%20Web%20Usability%20(Second%20Edition)%20(2006).pdf https://github.com/rajucs/Book-For-Programmers/blob/master/the-pragmatic-programmer.pdf

You can find it on GitHub https://github.com/rajucs/Book-For-Programmers/blob/master/the-pragmatic-programmer.pdf

It looks like all three books can be downloaded as PDF’s from this GitHub.

If the problem is that, u can use the https://github.com/labs42io/clean-code-typescript repo, they have great examples and each example has a how to use

Clean code typescript

I understand why people complain about it, but honestly, I think the ratio of good advice to bad advice is 9:1. For example, if you look at this summary of Clean Code (adapted for TypeScript), I think most people will agree that 90% of the guidelines are generally good ideas.

Also, I feel like using typescript helps to keep the code clean. Martin's book has mentioned already multiple times, but here's a typescript adaptation of it: https://github.com/labs42io/clean-code-typescript

The general ideas are fine, but the examples are pretty outdated. For modern SPA, CSS naming has become largely obsolete. A lot of the JS code shows the principles it is supposed to well but sadly includes other cruft.

Here's a guide I would recommend instead: https://github.com/labs42io/clean-code-typescript

https://github.com/labs42io/clean-code-typescript https://github.com/torokmark/design_patterns_in_typescript