Tutorials covering programming languages, type systems, architecture, tooling, and the patterns used to build software that lasts. Each chapter is standalone, built around real examples and verified facts.
React’s rendering process is a synchronous, recursive operation. When a component throws during render, React cannot simply catch the error and continue—the component tree may be in an inconsistent state, with some components mounted and others not, some hooks already called and others not. In React 15 and earlier, this inconsistency would corrupt React’s internal…
A procedural macro receives a flat stream of tokens. It cannot ask “is this a struct or an enum?” or “what are the field names?” at the token level. The syn crate parses that token stream into a typed syntax tree—DeriveInput, ItemFn, Expr, Type—so the macro can navigate the structure with Rust’s pattern matching and…
Normalization is the process of organizing a database’s columns and tables to reduce redundancy and eliminate the anomalies that redundancy causes. The theory is older than most of the databases that use it, but the practice is as relevant as ever: a table that stores a customer’s address on every order will eventually have two…
The browser renders a page in a pipeline: the style calculation, the layout, the paint, and the composite. Each stage costs time, and each stage can be the bottleneck. A CSS change that looks harmless in the source can trigger the expensive recalculation, the reflow of the whole page, or the repaint of the large…
The previous chapter covered the legacy experimental decorators — the version that required a compiler flag, relied on reflect-metadata, and powered frameworks like NestJS and TypeORM. This chapter covers the Stage 3 decorators, which TypeScript 5.0 shipped as the default. The new design is a near-rewrite of the legacy model: decorators receive a context object…
Micro-frontends apply the principle of service decomposition to the browser. Instead of one monolithic Vue application, the UI is split into independently developed, tested, and deployed fragments that a shell application composes at runtime. Module Federation is the mechanism that makes this composition practical: it allows a JavaScript application to expose modules to other applications…
The previous chapter covered the router’s event stream and the guards that gate navigation. Those are the mechanisms you use every day. But the Angular Router has a deeper set of features that solve specific, less common problems: standalone route components that lazy-load without loadChildren, route-level providers that scope services to a feature, component input…
Dart’s server-side ecosystem has no single ORM that dominates the way Hibernate dominates Java or ActiveRecord dominates Ruby. Instead, the landscape is a spectrum: raw drivers that speak the wire protocol, query builders that generate dialect-correct SQL, and ORMs that map tables to typed Dart classes with code generation. The choice between them is a…
A reverse proxy sits between the public internet and your application containers. It terminates TLS, routes requests by hostname or path, and forwards traffic to the appropriate backend. Containerizing it means the proxy itself becomes a service in the Compose stack, with its configuration mounted or baked into the image, and its lifecycle managed alongside…
The previous chapter covered the four decisions that shape a production Node.js image. This chapter goes deeper into the two that have the largest measurable impact: the multi-stage build structure that determines what ships, and the non-root execution model that determines what happens when something goes wrong. The size difference is not marginal. A single-stage…