Guides for programming and sysadmin.
Pick a topic and start reading.
Browse by topic
Pick a topic.
C++ (68 guides)
Modern C++ guides: C++20 and C++23 features, compilers, build systems, and measured performance.
Rust (9 guides)
Rust guides: async runtimes and embedded targets, with what actually runs under QEMU.
Go (27 guides)
Go guides: concurrency and testing, including the failure modes the compiler will not catch.
Python (54 guides)
Python guides: typing and packaging in real workspaces. The migration traps, in the order they bite.
TypeScript (1 guide)
TypeScript guides: strict-mode migrations across major versions, with the error counts.
Sysadmin (50 guides)
Linux systems work, measured: systemd, nginx, logrotate, containers, and the command line.
Latest guides
The newest guides, newest first.
-
Fix Rust E0308 "mismatched types" — Convert the Value, Fix the Signature, or Give Both Sides One Type Rust
Rust error E0308, mismatched types, means an expression produced one type where a different type was required: an i32 passed where an i64 belongs, if and else arms that disagree, a String where a &str belongs or the reverse, a value where a reference belongs, a stray semicolon turning a return value into (). This guide reproduces the error in its argument, return, branch, string, reference, and unit forms, shows the narrow set of conversions Rust performs automatically and the much larger set it refuses, and gives the fixes in the order to reach for them: change the type at the source, convert with From or Into where the conversion cannot lose data, try with TryFrom where it can, cast with as only with the loss priced in, and borrow or dereference where the mismatch is about access rather than value.
-
Fix Rust E0502 "cannot borrow as mutable because it is also borrowed as immutable" — End the First Borrow, Split the Work, or Restructure Rust
Rust error E0502, cannot borrow as mutable because it is also borrowed as immutable, means a shared borrow is still alive at the point where the code asks for a mutable borrow. This guide reproduces the error in its canonical form, its loop form, and its method-call form, shows the near-identical program the current compiler accepts because the first borrow has already ended, and gives the fixes in the order to reach for them: end or narrow the first borrow, split the work with an index loop or split_at_mut, restructure so a value is returned instead of a reference held, and clone only as a deliberate last resort.
-
Fix Rust E0382 "borrow of moved value" — Borrow Instead of Moving, Return the Value, or Clone on Purpose Rust
Rust error E0382, borrow of moved value, means a value was moved — into a function, another binding, a loop, or a closure — and the code then tried to use the original binding, which no longer owns anything. This guide reproduces the error in its function-call, assignment, loop, closure, and partial-move forms, shows exactly which uses survive a partial move and which do not, and gives the fixes in the order to reach for them: borrow instead of moving, return the value or restructure, take or replace a field, derive Copy only where copying is semantically right, and clone or share ownership only as a deliberate choice.
-
Fix C++ "request for member in pointer type" — Use -> on Pointers, and Why -> Cannot Fix a Non-Class Type C++
The GCC error request for member in a pointer type means the dot operator was used on a pointer: dot requires an object of class type, arrow requires a pointer to class type and is exactly equivalent to dereferencing first. This guide reproduces the dot-on-pointer failure and GCC's maybe you meant to use '->' suggestion, fixes it with the arrow and with the parenthesized dereference form, shows why the unparenthesized star form fails on precedence, covers the sibling non-class type error where the pointee has no members and arrow does not help, and ends with references and std::unique_ptr, where dot and arrow both compile but reach different objects.
-
Fix C++ "no match for 'operator<<'" — Streaming a User-Defined Type and a std::vector of It to std::cout C++
Streaming a user-defined type to std::cout fails with no match for 'operator<<' because std::basic_ostream provides overloads only for built-in types, character data, and a few library types. This guide reads the exact GCC error, fixes it with a non-member operator<< taking (std::ostream&, const T&) and returning std::ostream& so chaining works, shows the friend-defined-inside-class form for private members, adds a separate overload for a std::vector of the type, and shows why a non-const reference parameter breaks streaming of const objects.
-
Fix C++ "invalid conversion from 'const char*' to 'char*'" — Add const, Copy the Text, or Own It in std::string C++
The GCC error invalid conversion from 'const char*' to 'char*' means read-only text was handed to code that claims the right to modify it: a string literal, a const char* variable, or the result of c_str() was assigned to a char* or passed to a char* parameter. This guide reproduces the error in all three forms, explains why GCC reports the literal form with different wording and only as a warning by default, and gives the four correct fixes in order: declare const char* when nothing writes, copy into a local char array when a callee really writes, store the text in std::string and use data() when it must be owned and mutable, and reserve const_cast for the one narrow legacy case where the underlying object is genuinely mutable.
-
Fix C++ "'cout' was not declared in this scope" — Missing
, Missing std::, and the using namespace std Trade-Off C++The error 'cout' was not declared in this scope has two different causes with the same first line: no
included at all, or included but cout used without std:: qualification, because std::cout lives in namespace std and its name is not injected into the global scope. This guide reproduces both failures with GCC, reads the did-you-mean suggestion that only the second failure earns, fixes both with std::cout, covers std::endl versus a newline character, shows the using namespace std form and why it stays out of headers, and ends with the wrong-header trap where provides std::printf but not std::cout. -
Fix C++ "cannot convert 'std::string' to 'const char*'" — c_str(), data(), and When the API Wants char* C++
Passing a std::string where a const char* is expected fails because there is no implicit conversion from std::string to a character pointer. This guide reads the exact GCC error at a real std::fopen call, fixes it with c_str() for read-only APIs, shows why c_str() still fails for a char* parameter while data() on a non-const string works since C++17, and states the invalidation rule that ends the useful life of every pointer these functions return.
Tools
Small checkers and verifiers that run in your browser. Paste input, get a verdict — no sign-up, no upload.
systemd Unit Checker
Paste a [Service] section and get a plain-language verdict on every sandboxing setting it finds.
sshd_config Verifier
Paste sshd -G output and get a hardening verdict on the values your server actually runs.
Sanitizer Report Decoder
Paste an AddressSanitizer, UBSan, or ThreadSanitizer report and get the bug, the file and line, and the fix.
nginx Server-Block Auditor
Paste a server block and get WebSocket, TLS, HSTS, and proxy-header verdicts, each tied to the nginx.org reference.
OnCalendar Validator
Paste a systemd timer expression and get the specific reason it fails and its normalized form, plus the past-date traps the built-in check hides.
Sudoers Config Checker
Paste a sudoers file or sudoers.d drop-in and get a per-line verdict before it ever touches /etc/sudoers.