Guides & Courses

A package manager is one of the most architecturally rich pieces of tooling you can build. It touches dependency resolution (a provably NP-complete problem in the general case), distributed systems (registry protocol, caching), cryptography (integrity verification, signing), filesystem management (content-addressable stores, atomic installs), and UX design (CLI, error messaging). This guide covers every layer, with concrete algorithms and data structures, not hand-waves.

A complete reference for zypher-cli and zypher framework

A deep dive into the Unix/Linux text toolchain — grep, sed, awk, cat, echo, cut, tr, sort,uniq, wc, tee, less, head, tail, printf, xargs, find, diff, patch, strings, hexdump, and more.

The Complete Guide to creating A UI Library Using Only C and SDL2

How do servers handle thousands of connections? Learn readiness-based I/O with select/poll/epoll, common edge cases, and build a tiny event loop in C, Zig, and Rust.

A comprehensive guide to mastering Emacs, covering everything from basic concepts to advanced customization and workflow optimization.

A Comprehensive Guide from First Principles to a Complete 3D Renderer

Language-agnostic & pattern-driven. Every step describes what to build, why it is designed that way, and which Gang of Four (GoF) design pattern governs it. Pseudocode is intentionally simplified — the focus is on architecture decisions, data structures, and the relationships between components. Real implementation can be done in any language capable of systems or application programming (Python, Go, Rust, Java, TypeScript, etc.). The framework we are building is comparable in scope to Django, Rails, or Laravel, a full-stack, batteries-included web framework with an ORM, templating engine, form validation, authentication, caching, migrations, a CLI, and an admin interface.

build systems guide. Why they matter, why should you even care, significatincy and much more

Language-agnostic & pattern-driven. Every step describes what to build, why it is designed that way, and which Gang of Four (GoF) design pattern governs it. Pseudocode is intentionally simplified — the focus is on architecture decisions, data structures, and the relationships between components. Real implementation uses the same logical structure in any language (Rust, C++, TypeScript, Python, Go, etc.).

Architecture-focused. Every step describes *what* to implement and why, with concrete data-format references, assembly/pseudocode examples, and memory-layout diagrams so you can build it in x86 Assembly + C (the most common pairing), or adapt to ARM/RISC-V. Tools used; NASM, GCC (cross-compiler), QEMU, GNU ld.

Architecture-focused. Every step describes what is involved and the role it plays in clean architecture

Building Professional 2D Games with SDL in C. A Comprehensive Resource Management and Rendering System.

Mastering the C Preprocessor for Portable and Kernel-Level Code. A Comprehensive Resource for Cross-Platform Development and Linux Kernel Programming.

A Data-Oriented Approach to Game Development with SDL in C. Building High-Performance Games with Entity Component Systems.

Language-agnostic. Every step describes what to implement and why, with pseudocode and concrete data-format references so you can implement it in any language (Python, Rust, Go, C, TypeScript, etc.).

The Complete Guide to Graphics and Games Programming with SDL in C. A Comprehensive Journey from Pixels to Professional Game Development.