Awesome-Reading-List VS clean-code-typescript

Check some of the articles I link here: https://github.com/EanNewton/Awesome-Reading-List

I've been thinking about doing this for a while. I've been keeping things like these on my GitHub (https://github.com/EanNewton/Awesome-Reading-List and https://github.com/EanNewton/Awesome-Keebs) but did just rebuild my homelab and stand up some domains on it so good timing for setting up a blog.

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