A structured weekend checklist for mastering large-scale UI system design interviews. Focus: Think in systems, not just code.
Discover gists
| """ | |
| 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 |
| Adobe Acrobat Pro DC License Key |
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.
| #single video | |
| youtube-dl --cookies youtube.com_cookies.txt "URL" | |
| #playlist | |
| youtube-dl --yes-playlist --cookies youtube.com_cookies.txt "URL" | |
| You can use: --playlist-start, --playlist-end, --playlist-reverse or --playlist-items to achieve this goal. | |
| #Note: cookie should be in Netscape format |
Lecture 1: Introduction to Research — [📝Lecture Notebooks] [
Lecture 2: Introduction to Python — [📝Lecture Notebooks] [
Lecture 3: Introduction to NumPy — [📝Lecture Notebooks] [
Lecture 4: Introduction to pandas — [📝Lecture Notebooks] [
Lecture 5: Plotting Data — [📝Lecture Notebooks] [[
Практический сетап для ситуации, когда проводного интернета нет, доступна только LTE-связь, обычные VPN/VLESS-конфигурации работают нестабильно, а нормальный доступ в интернет нужен сразу для нескольких устройств — в том числе для работы через корпоративные VPN.
Это не универсальная инструкция и не «правильная архитектура на все случаи жизни». Ниже описан конкретно мой сетап, который сейчас работает у меня и который можно использовать как отправную точку.
Поддержать можно:
- BTC
bc1q6r9tdctf2wjrhj03w0u8lrg3gs2m8fkvcv4953 - USDT (TRC20)
TK29wf2q2pBtm4rFDPkVqfBoNKdKR7qMXS
| #!/bin/bash | |
| # Define colors | |
| RED=$(tput setaf 1) | |
| GREEN=$(tput setaf 2) | |
| BLUE=$(tput setaf 4) | |
| YELLOW=$(tput setaf 3) | |
| RESET=$(tput sgr0) | |
| # Function to handle errors |