C++20 & Forward Rendering
Build the Fedora/OpenGL 4.3+ foundation, then work through matrices, shaders, lighting, and the rendering pipeline. Keep the core renderer implementation as deliberate practice.
Open Renderer Project StructureHome base for current learning and project work. Start with Current Focus, then use the technology tracks for the questions, projects, and references behind each phase. Milestones and exercises live in the Practice Guide; dated plans live in the Momentum Schedule.
Six starting points for your current engineering and applied Python work. These are learning and project tracks, not automatically tracked progress.
Build the Fedora/OpenGL 4.3+ foundation, then work through matrices, shaders, lighting, and the rendering pipeline. Keep the core renderer implementation as deliberate practice.
Open Renderer Project Structure30–40 focused hours across endpoint configuration in staff/API/D1, minute-level probing and durable history, then timezone-aware daily summaries published to KV for a public status and history view.
Open Uptime SchedulePrioritize vectors, matrices, transformations, and numerical behavior that connect directly to your renderer and future GPU simulations.
Open Math GuidesStrengthen RAII, copy/move semantics, STL fluency, debugging, and resource ownership. Practice transferable C++ decisions and delegate familiar scaffolding.
Open Practice GuideExplore Steam and NBA/NFL/NCAA data: clean and combine small CSV/JSON datasets, investigate trends, and tell a clear story with charts. Make your workflow rerunnable without building a heavyweight data platform.
Build reproducible data preparation and feature pipelines, then evaluate simple models for game reception or sports outcomes against strong baselines. Guard against leakage and use time-aware validation.
Explore Machine Learning ExercisesOrdered by current priority. Each phase lists the questions you should be able to answer, the projects that use it, and its references. Milestones and exercises live in the Practice Guide; dated plans live in the Momentum Schedule.
The canonical list, each with a paired exercise and follow-ups.
Practice Guide · C++ →Sequenced as the eight-week Forward Renderer track; architecture, ownership, and build setup live in Project Structure.
Momentum Schedule · Renderer →Renderer Project Structure →The canonical list, each with a paired exercise and follow-ups.
Practice Guide · Lua →The canonical list, each with a paired exercise and follow-ups.
Practice Guide · Godot →Use when ownership, const correctness, object lifetime, templates, undefined behavior, or a standard-library detail needs a deeper explanation.
Targets, include paths, linking, visibility, presets, toolchain files, subdirectories, and the commands used to structure C++ builds.
Manifest mode, dependency restoration, triplets, toolchain integration, package features, and reproducible project setup.
Context setup, buffers and VAOs, shaders, transforms, cameras, lighting, and debugging, written against the modern core profile.
Per-function behavior, parameters, and errors. Check each page’s version table: this project targets 4.3, so avoid 4.5-only entry points such as DSA.
The authoritative source for qualifiers, interface blocks, built-ins, layout rules, and compute-shader semantics when a tutorial is ambiguous.
Frame capture and inspection of draw calls, pipeline state, buffers, and textures — the first tool to reach for on a black or wrong frame.
Tables, functions, metatables, coroutines, modules, the C API stack, protected calls, and embedding behavior.
Nodes, resources, 3D rendering, ShaderMaterial, SubViewport, RenderingDevice, storage buffers, and compute workflows.
A structured path through color math, coordinates, patterns, noise, animation, and learning to think in shader space.
Procedural graphics, signed-distance fields, raymarching, noise, lighting, and compact mathematical techniques to revisit as needed.
The canonical list, each with a paired exercise and follow-ups.
Practice Guide · Hono →Routing, context, middleware, typed bindings, validation, JSX, and error handling. Small enough to read narrowly as the application grows.
Execution model, scheduled handlers, waitUntil, bindings, environments, secrets, platform limits, and deployment behavior.
Migrations, prepared statements, indexes, query behavior, local development, backups, and relational storage limits.
Eventually consistent reads, namespace bindings, expiration, metadata, limits, and the tradeoffs behind current-status snapshots.
Runtime-faithful tests for bindings, scheduled handlers, D1, KV, service bindings, and request behavior inside Workers.
The canonical list, each with a paired exercise and follow-ups.
Practice Guide · TypeScript + Vue →The canonical list, each with a paired exercise and follow-ups.
Practice Guide · Go →Everyday types, narrowing, generics, and module resolution — the sources cited throughout the TypeScript milestones.
Single-file components, reactivity, watchers, composables, props/emits, and provide/inject.
A Tour of Go, Effective Go, and the standard-library packages (net/http, encoding/json, database/sql) used by the Go milestones.
A typed dashboard with player search, season stats, recent games, compact charts, and live-data states.
A Go and Vue application that turns library and achievement data into treemaps, bubble charts, rarity views, and overlap comparisons.
A landscape sandbox with layered noise, height-based materials, lighting controls, and room for erosion, rivers, biomes, and LOD.
A terrain-based weather laboratory where the user can adjust temperature, humidity, pressure, wind, cloud cover, precipitation, sunlight, and terrain parameters to generate different atmospheric conditions in real time. An alternate real-world mode accepts a ZIP code, retrieves the location’s current weather, and recreates those conditions across the simulated terrain. The project joins meteorology and atmospheric physics with numerical simulation, procedural terrain, shaders, particles, volumetric effects, data visualization, and graphics-engine architecture.