notnotrobby

Computer Graphics Programming Resources

List of freely available resources to study computer graphics programming.

Table of Contents

• Learning Path
• Foundations
  • Getting Started
  • C++
• Mathematics

danrovito

<label for="country">Country</label><span style="color: red !important; display: inline; float: none;">*</span>      
        
            <select id="country" name="country" class="form-control">
                <option value="Afghanistan">Afghanistan</option>
                <option value="Åland Islands">Åland Islands</option>
                <option value="Albania">Albania</option>
                <option value="Algeria">Algeria</option>
                <option value="American Samoa">American Samoa</option>
                <option value="Andorra">Andorra</option>
                <option value="Angola">Angola</option>

j-mai

Using Git with Unity

What are the problems?

• Noise: Unity editor has lots of temporary files that we don’t want git to track
• Broken object references: Unity keeps track of objects created by using random GUIDs, and if they aren’t tracked using .meta files then there can be conflicts that really break your project
• Unresolvable merge conflicts: files like scene files that are written in confusing languages (like YAML) that are supposed to be translations of Unity editor actions into code. Most likely, you cannot resolve using Git, and the only way to resolve merge conflicts is to open it in a text editor and resolve them manually while hoping you don't mess anything up because these files are confusing and not meant to be manipulated directly.
• Large files: Sometimes assets are large and take up a lot of storage space

💻 Project Setup

aras-p

// Just before switching jobs:
// Add one of these.
// Preferably into the same commit where you do a large merge.
//
// This started as a tweet with a joke of "C++ pro-tip: #define private public",
// and then it quickly escalated into more and more evil suggestions.
// I've tried to capture interesting suggestions here.
//
// Contributors: @r2d2rigo, @joeldevahl, @msinilo, @_Humus_,
// @YuriyODonnell, @rygorous, @cmuratori, @mike_acton, @grumpygiant,

nitrocode

Easter Eggs & Hidden Features in Claude Code

A collection of easter eggs, undocumented behaviors, internal codenames, and surprising details found in the Claude Code source code. Organized by category.

---

Table of Contents

1. The Buddy / Companion Pet System

wojteklu

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.

---

General rules

1. Follow standard conventions.
2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
3. Boy scout rule. Leave the campground cleaner than you found it.
4. Always find root cause. Always look for the root cause of a problem.

Design rules

grahamhelton

#!/bin/bash
# Detect all subjects with nodes/proxy permissions

# Colors
NOCOLOR=$(tput sgr0)
RED=$(tput setaf 1)
GREEN=$(tput setaf 2)
YELLOW=$(tput setaf 3)
CYAN=$(tput setaf 6)
DIM=$(tput setaf 8)

NARKOZ

Motherfucking Websites

A concise list of the Motherfucking-style sites — because sometimes the web needs blunt, unapologetic clarity.

• https://motherfuckingwebsite.com
  The original. Uses plain HTML, no bullshit. Says exactly what it needs to say and nothing more.

• http://bettermotherfuckingwebsite.com
  An improved variant. Slightly nicer layout, still minimal and unapologetic. Better copy, same attitude.

karpathy

LLM Wiki

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.

The core idea

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.