Corpus
Writing, maintained knowledge, sketches, and other material from engineering and learning.
01 / Editorial roles
Different formats for different purposes. These distinctions stay stable as individual entries change.
Case studies, essays, and writing where sequence and perspective matter.
ExploreConcepts, guides, and structured notes intended to remain useful as understanding evolves.
ExploreDiagrams and drawings used to explain systems, relationships, and concepts.
Explore02 / Featured from the corpus
Representative pieces chosen deliberately rather than driven by recency. The selection can mix Writing, Knowledge, and Sketches without a fixed item cap.
A closer look at the KrakenD work: how gateway configuration and deployment were structured across environments, and the trade-offs involved in making those changes repeatable and reviewable.
A reference for designing repeated requests so retries do not create repeated effects.
A visual model of how structured KrakenD configuration moves from source templates through environment-specific builds and deployment.
An internal playground where analysts could test assessment-rule changes without production access or one-off engineer scripts.
A compact mental model for identifying where independently changing components become a distributed-systems problem.
A system-design sketch showing how a client obtains an authorization code and exchanges it for an access token before reading protected API data.
The Atlas cuts across both sides of the site: follow relationships between work, writing, knowledge, sketches, projects, contributions, and credentials.
03 / Latest corpus updates
Derived from shared content metadata; typo-only or metadata-only churn should not reorder this list.
A practical guide to choosing a skill, reducing practice friction, and turning reading into a durable result.
A guide to naming which parts of a system can fail together and which consequences cross the boundary.
A compact mental model for identifying where independently changing components become a distributed-systems problem.
A visual model of how structured KrakenD configuration moves from source templates through environment-specific builds and deployment.
A reference for designing repeated requests so retries do not create repeated effects.
A system-design sketch showing how a client obtains an authorization code and exchanges it for an access token before reading protected API data.
A short reference for locating the boundary at which independently changing parts need an explicit contract.
A teaching sketch for separating client, API, model, and inference boundaries when a full-stack product uses local, hosted, or managed AI services.
A reference for distinguishing delivery guarantees from the application behavior built on top of them.
An overview of the names, interfaces, and boundaries that shape communication between containers.
A compact reference for choosing between addition, multiplication, and inclusion-exclusion when counting possibilities.
A reference for reading a distribution as a model of possible outcomes rather than a list of guaranteed events.
An overview of how regulated genetic expression contributes to observable traits through multiple biological layers.
A system architecture sketch connecting application services, OpenTelemetry, logs, metrics, traces, and observability storage and visualization tools.
A Coding Camp 2025 capstone sketch connecting recipe extraction, preprocessing, model training, database seeding, and scheduled deployment workflows.
A Coding Camp 2026 capstone sketch showing a client, Express service, FastAPI inference service, PostgreSQL database, and prediction request flow.
A Coding Camp 2026 teaching sketch comparing client, API, model, database, and language-model boundaries across local, public, and hosted services.
A Coding Camp 2026 capstone sketch connecting survey data, user profiles, investor preferences, categorization, APIs, and a machine-learning model.
A system architecture sketch for a personalized fitness application that combines a mobile client, backend API, image classification, recommendations, and an optional hosted language model.
A delivery architecture sketch connecting GitHub, Jenkins, Ansible, Docker, a container registry, and Kubernetes deployment steps.
A practical way to keep environment-specific configuration reviewable instead of hiding differences in generated artifacts.
A Coding Camp 2025 capstone sketch for an automated machine-learning training pipeline driven by APIs, scheduled jobs, scripts, and webhooks.
How to choose migration boundaries when correctness matters more than moving every component at once.
A triage method for deciding which technical sources deserve deep reading, a summary, reference status, or release.
How to tell when repeated local fixes are no longer reducing the problem and a known-good rebuild deserves consideration.
A Coding Camp 2025 capstone sketch connecting travel discovery, weather and hotel models, scraped data, scheduled jobs, and a shared database.
A Coding Camp 2026 capstone sketch for a client, user-management API, AI service, database, and image-based inference flow.
Why a short system assessment helps before a team commits to a rewrite.
A small scenario playground can make rule changes reviewable without giving every experiment access to production execution.
A Coding Camp 2026 capstone sketch showing a client, Node.js service, MongoDB, model training data, and the transition from local development to hosted deployment.
No matching entries.
