List of freely available resources to study computer graphics programming.
Discover gists
EDIT: Well this has been linked now so just an FYI this is still TBD. Feel free to comment if you have suggestions for improvements. Also here is an unrolled Twitter thread of a lot of the tips I talk about on here.
I've been doing frontend for a while now and one thing that really gripes me is the interview. I think the breadth of knowledge of a "Frontend Engineer" has been so poorly defined that people really just expected you to know everything. Many companies have made this a hybrid role. The Web is massive and there are many MANY things to know. Some of these things are just facts that you learn and others are things you really have to understand.
Every time I interview, I go over the same stuff. I wanted to create a gist of the TL;DR things that would jog my memory and hopefully yours too.
Lots of these things are real things I've been asked that caught me off guard. It's nice to have something you ca
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.
| [os.symbols] | |
| AIX = "βΏ " | |
| Alpaquita = "π " | |
| AlmaLinux = "ο " # nf-linux-almalinux | |
| Alpine = "ο " # nf-linux-alpine | |
| Amazon = "π " | |
| Android = "ο » " # nf-fa-android | |
| Arch = "ο " # nf-linux-archlinux | |
| Artix = "ο " # nf-linux-artix | |
| Bluefin = "π " |
#!/bin/bash
# Welcome interface
function show_welcome() {
echo "###############################################"
echo "# #"
echo "# Welcome to the Cloudflare IP Optimization Tool #"
echoWhether you're curating reference images, building a wallpaper collection, or archiving artwork, the challenges are the same: finding content, organizing it consistently, and keeping it accessible. A well-planned collection strategy saves hours of searching and reorganizing later.
the rule34.ink gallery β The first step in any collection is sourcing. Booru sites offer the most consistent metadata, making them ideal starting points. Batch downloading tools can pull images by tag, artist, or rating filter. Prioritize sources that provide structured metadata β tags, artist names, character names β because this information is difficult to reconstruct later. Cross-reference downloads across multiple boorus to catch content that might be exclusive to one platform. Always verify image quality before archiving; blurry or compressed images waste storage and reduce the value of your c
- Whether you're curating reference images, building a wallpaper collection, or archiving artwork, the challenges are the same: finding content, organizing it consistently, and keeping it accessible. A well-planned collection strategy saves hours of searching and reorganizing later.
rule34.ink image search β Sourcing efficiently means knowing which platforms cover which content. Niche character art might only appear on specialized boards, while popular series are well-covered across multiple platforms. Aggregation platforms that index multiple boorus simplify discovery, letting you search once and collect from many sources. Build a source priority list based on image quality, metadata completeness, and search interface quality.
See how a minor change to your commit message style can make a difference.
git commit -m"<type>(<optional scope>): <description>" \ -m"<optional body>" \ -m"<optional footer>"