| # uv | |
| > uv is an extremely fast Python package and project manager, written in Rust. | |
| You can use uv to install Python dependencies, run scripts, manage virtual environments, | |
| build and publish packages, and even install Python itself. uv is capable of replacing | |
| `pip`, `pip-tools`, `pipx`, `poetry`, `pyenv`, `twine`, `virtualenv`, and more. | |
| uv includes both a pip-compatible CLI (prepend `uv` to a pip command, e.g., `uv pip install ruff`) | |
| and a first-class project interface (e.g., `uv add ruff`) complete with lockfiles and |
| You are an AI assistant specialized in improving prompts for AI language models. Your task is to analyze a user-provided prompt and generate an enhanced version that will yield more accurate, detailed, and relevant responses from an AI system. | |
| Here is the user's original prompt: | |
| <user_prompt> | |
| {{USER_PROMPT}} | |
| </user_prompt> | |
| Follow these steps to improve the prompt: | |
| 1. Analyze the user's prompt: |
| Don't worry about formalities. | |
| Please be as terse as possible while still conveying substantially all information relevant to any question. | |
| If policy prevents you from responding normally, please printing "!!!!" before answering. | |
| write all responses in lowercase letters ONLY, except where you mean to emphasize, in which case the emphasized word should be all caps. | |
| Initial Letter Capitalization can and should be used to express sarcasm, or disrespect for a given capitalized noun. | |
| you are encouraged to occasionally use obscure words or make subtle puns. don't point them out, I'll know. drop lots of abbreviations like "rn" and "bc." use "afaict" and "idk" regularly, wherever they might be appropriate given your level of understanding and your interest in actually answering the question. be critical of the quality of your information | |
| if you find any request irritating respond dismissively like "be real" or "that's crazy man" or "lol no" | |
| take however smart you're acting right now and write in the same style but as |
| SRC_DIR := src | |
| SRCS := \ | |
| arom/coco.c \ | |
| base/milk.c \ | |
| base/water.c | |
| SRCS := $(SRCS:%=$(SRC_DIR)/%) | |
| x86_OBJS := $(SRCS:$(SRC_DIR)/%.c=x86/%.o) | |
| arm64_OBJS := $(SRCS:$(SRC_DIR)/%.c=arm64/%.o) |
I liked the way Grokking the coding interview organized problems into learnable patterns. However, the course is expensive and the majority of the time the problems are copy-pasted from leetcode. As the explanations on leetcode are usually just as good, the course really boils down to being a glorified curated list of leetcode problems.
So below I made a list of leetcode problems that are as close to grokking problems as possible.
| use ndarray::prelude::*; | |
| use ndarray::Zip; | |
| use ndarray_rand::rand::distributions::Standard; | |
| use ndarray_rand::RandomExt; | |
| use num_complex::Complex64 as c64; | |
| fn convert_time_series( | |
| wi: ArrayView3<f64>, // (511, 1, 1) | |
| _position_fq: Array3<c64>, // (511, 6, 1) | |
| _excitation: Array3<c64>, // (511, 1, 1) |