zero_to_gpt VS pls

The deep learning book is a great choice, as many have mentioned.

I've been making a course that has a little less theory, and a little more application here - https://github.com/VikParuchuri/zero_to_gpt . Videos are all optional (cover the same content as the text).

I've been putting a course together that teaches deep learning from the ground up - https://github.com/VikParuchuri/zero_to_gpt . It includes theory and code, and tries to strike a balance between the two.

It focuses on text models over image models (rnn, transformer, etc).

It's not 100% finished, but has enough to get you very far.

I'm in the process of creating a deep learning course called Zero to GPT - https://github.com/VikParuchuri/zero_to_gpt .

It teaches you everything you need to train your own LLM, including the basics of deep learning and linear algebra. You learn the theory and the application, so you have a strong grounding in what you're doing. It includes written explanations, diagrams, and videos.

I'm up to transformers now - only a few more lessons to go. It's been fun to write, but balancing time spent training models with writing the course has been hard. Hopefully I will get the time to finish it soon.

Many PR about typos fixing or installing GitHub actions to validate spellchecking on various repositories fix typos #4 ccoVeille posted on Apr 15, 2024 Fix typos and style Format README.md file View on GitHub Add Typos GitHub Action #37 ccoVeille posted on Apr 19, 2024 https://github.com/marketplace/actions/typos-action Fixes #28 View on GitHub fix typos #113 ccoVeille posted on Apr 13, 2024 Fix typos in code and tests Fix acronyms and brand names View on GitHub fix typos, brands and acronyms #21 ccoVeille posted on Apr 01, 2024 fix typos in code, test and documentation Fix registered trademark and other acronyms View on GitHub Fix typos in the documentation and code comments #99 ccoVeille posted on Apr 21, 2024 View on GitHub typos suggestion #390 ccoVeille posted on Apr 22, 2024 Check list [X] I have performed a self-review of my code [ ] I have commented my code in hard-to-understand areas [X] I have made corresponding changes to the documentation Description Fix some typos and wordings in README.md Fix headers style Fix exemplī grātiā usage (Latin) Type of change [ ] Bug fix [ ] New feature [ ] Refactor [ ] Breaking change [X] Documentation change Test environment Shell [ ] bash [ ] zsh [ ] fish OS [ ] Linux [ ] Mac OS X [ ] Windows [ ] Others: View on GitHub Fix typo and style #3 ccoVeille posted on Apr 25, 2024 View on GitHub

I'm working on pls (https://github.com/dhruvkb/pls/), a prettier and more powerful alternative to ls(1) that adds a lot of customisation and provides a very fluent command-line interface. It aims to be a superset of exa in terms of the features, while being more actively maintained and targeting a smaller subset of pro-users.

It works quite well and is very usable as a daily driver. I'm adding more features to it and making it available to install it via platform-native package managers.

I made a small CLI tool called pls (repo). It's a FOSS app for listing the contents of your directory (similar to ls) but it has lots of nifty features geared towards professionals/programmers (hence the 'p' in the name) that make the output prettier and easier to visually parse.