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.
A loading state is not a spinner. It is a contract between the application and the user: the application has accepted the request, is working on it, and will show the result as soon as it is ready. The traditional way to implement this contract is a boolean flag—const [isLoading, setIsLoading] = useState(true)—checked at the…
Rust has three kinds of procedural macros, and the derive macro covered in the previous chapter is only the first. The other two—attribute-like macros and function-like macros—share the same crate type and the same TokenStream interface, but they are invoked in different syntactic positions and receive different inputs. An attribute-like macro is written as #[route(GET,…
Every query that filters rows makes the same fundamental choice: read the whole table and check each row, or use an index to jump directly to the rows that match. The optimizer makes this decision on every query, and the choice determines whether the query takes milliseconds or minutes. Three access methods dominate: the table…
A legacy application has years of CSS. The stylesheets are the thousands of lines, the selectors are the deep and the specific, the class names are the semantic (.btn-primary, .card-header), and the cascade depends on the load order that only the original author understood. The Tailwind adoption cannot be the big-bang rewrite; the application is…
Decorators are a language feature that attaches metadata or behavior to classes, methods, properties, and parameters. TypeScript has had two versions of this feature: the legacy experimental version, which required the experimentalDecorators compiler flag and was never standardized, and the standard Stage 3 version, which TypeScript 5.0 shipped as the default. The legacy version is…
Nuxt’s power comes not just from routing and data fetching, but from three interlocking systems that make the framework extensible, deployable, and ergonomic. Modules let you package and share framework modifications. The Nitro server engine compiles your server code into a standalone output that runs anywhere. Auto-imports eliminate the boilerplate of explicit imports while preserving…
The Angular Router is one of the framework’s most used features and one of its least understood. You configure routes, navigate with routerLink, and read parameters from ActivatedRoute. That is the API surface most developers interact with. But underneath, the router is a state machine that runs through a specific sequence of events for every…
Protocol Buffers is a language-neutral, platform-neutral mechanism for serializing structured data. In Dart, using it requires two distinct pieces: the protoc compiler with the Dart plugin, which generates the Dart source code from a .proto file, and the protobuf runtime package, which the generated code depends on to serialize and deserialize the messages . The…
A database container is not like a web server container. The web server is stateless—kill it, restart it, and it serves the same content. The database holds state, and the entire value of the containerization exercise depends on that state surviving. Docker’s default filesystem is ephemeral: when the container is removed, everything written inside it…
A Node.js application containerized naively produces an image over a gigabyte, runs as root, ships every dev dependency and the TypeScript compiler into production, and ignores SIGTERM when Docker tries to stop it gracefully. Each of these is fixable with a few Dockerfile lines, and the fixes are not new—multi-stage builds have existed since 2017—yet…