clean-code-typescript VS build-your-own-x

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

View on GitHub

✅ codecrafters-io/build-your-own-x : https://github.com/codecrafters-io/build-your-own-x

8) Build Your Own X: Unleash your inner inventor and embark on a journey of self-creation with this collection of project ideas for building your own software, tools, and even operating systems. Fuel your entrepreneurial spirit and learn valuable engineering principles by bringing your innovative ideas to life. (https://github.com/codecrafters-io/build-your-own-x)

Also if we can someone merge this level of detail/guidance with the projects on https://codecrafters.io/, i would easily pay for something like that.

Build your own X is another useful resource for a curious mind.

This is what you're looking for: Build your own X!