Version control is a system that records changes to a file or set of files over time so that you can recall specific versions later.
If you are a developer and want to keep every version of your code/project (which you would most certainly want to), a Version Control System (VCS) is a very wise thing to use.
Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.
| """ | |
| The most atomic way to train and run inference for a GPT in pure, dependency-free Python. | |
| This file is the complete algorithm. | |
| Everything else is just efficiency. | |
| @karpathy | |
| """ | |
| import os # os.path.exists | |
| import math # math.log, math.exp |
gh CLI。
| <?xml version="1.0" standalone="yes"?> | |
| <LaunchBox> | |
| <Game> | |
| <ID>3d183397-20d4-4f32-8fe8-41fd230bb3a2</ID> | |
| <Title>Baryon</Title> | |
| <ReleaseDate>1995-01-01T17:21:48+02:00</ReleaseDate> | |
| <Rating /> | |
| <Genre>Shooter</Genre> | |
| <Platform>MS-DOS</Platform> | |
| <Developer>ACRO Studio</Developer> |
| Privacy Policy for [Bot Name] | |
| This Privacy Policy governs the collection, use, and sharing of personal information by [Bot Name], a Discord bot developed by [Developer Name]. By using [Bot Name], you agree to the terms of this Privacy Policy. | |
| Information We Collect | |
| We collect information that you provide to us through your use of the bot, such as your Discord user ID and username, server and channel information, and message content. We may also collect usage data, such as the frequency and duration of your use of the bot. | |
| How We Use Your Information |
| TERMS OF SERVICE AGREEMENT | |
| This Terms of Service Agreement (the "Agreement") is entered into between [Anshul Chauhan] ("Bot Owner") and the user ("User") of the [Bot Name] Discord bot (the "Bot"). | |
| By using the Bot, the User agrees to be bound by the terms of this Agreement. If the User does not agree to the terms of this Agreement, they should immediately discontinue use of the Bot. | |
| 1. Use of the Bot: The Bot Owner grants the User a non-exclusive, non-transferable, limited license to use the Bot for personal or non-commercial purposes. | |
| 2. Prohibited Use: The User may not use the Bot in any way that violates applicable laws, rules, or regulations or infringes upon the rights of any third party. The User may not use the Bot for any commercial purposes without the express written consent of the Bot Owner. | |
| 3. Limitation of Liability: The Bot Owner shall not be liable for any damages arising out of the use or inability to use the Bot, including but not limited to, damages for loss of profits, loss of data, or o |
A pattern for building personal knowledge bases using LLMs.
This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.
Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.
| #include <stdio.h> | |
| #include <fcntl.h> | |
| #include <stdlib.h> | |
| #include <sys/ioctl.h> // for _IOW, a macro required by FSEVENTS_CLONE | |
| #include <sys/types.h> // for uint32_t and friends, on which fsevents.h relies | |
| #include <unistd.h> | |
| #include <string.h> // memset | |
| //#include <sys/_types.h> // for uint32_t and friends, on which fsevents.h relies | |
| #include <sys/stat.h> // for mkdir |