Novus Stream Solutions

Category

Stack & engineering

The locked, opinionated stack behind the Novus ecosystem and how it is built — code-as-content architecture, type-safe content, edge rendering, and the AI-assisted engineering workflow that ships it solo.

23 articles

23 articles in this thread

  1. A ladder of feature-flag techniques from an environment variable to a typed config module to a hash-based percentage rollout splitting traffic without an external platform

    Stack & engineering · Jun 29, 2026

    Feature flags without a platform

    A three-rung ladder for shipping behind flags on a small product — env vars, a typed flag module, hash-based percentage rollouts — plus the cleanup rules that stop flag debt.

    Novus Stream Solutions (hub)

  2. Three innovation tokens above a technology stack whose data, auth, and payments layers are marked boring and stable while a small leaf component is flagged for experimentation

    Stack & engineering · Jun 28, 2026

    The case for boring technology

    Why a small operation should spend its innovation tokens on the one thing that differentiates it and choose deliberately boring technology everywhere money, data, and login are involved.

    Novus Stream Solutions (hub)

  3. A ten-line decision record passing along a timeline from a developer writing it at decision time to the same developer reading it months later inside a code repository

    Stack & engineering · Jun 27, 2026

    Documenting decisions: the ten-line ADR that saves future you

    A ten-line architecture decision record scaled to a team of one: the template, the threshold for writing one, and the case for keeping the files in the repo instead of a wiki.

    Novus Stream Solutions (hub)

  4. A monthly reliability gauge partly spent beside a short handwritten incident log, illustrating an error budget sized for a one- or two-person team

    Stack & engineering · Jun 26, 2026

    Error budgets for tiny teams: reliability without an SRE org

    Scaling the error-budget idea down to a one- or two-person operation: the arithmetic of nines at small revenue, a written not-fixing list, six-line incident notes, and spending unused budget on shipping speed instead of hoarding it.

    Novus Stream Solutions (hub)

  5. One large app bundle split into a small initial shell plus many per-route chunks that load only when a tool is opened, with the AI model deferred until first use

    Stack & engineering · Jun 16, 2026

    Code-splitting a large web app: how lazy routes keep it fast

    How the NSS Background Remover stays fast to open despite many tools: route-level code-splitting so each tool is its own chunk, lazy boundaries that defer the heavy parts, deferring multi-megabyte AI models until a tool actually needs them, and the measurements that tell you whether any of it worked.

    NSS Background Remover

  6. A memory-over-time chart where a naive export climbs past a tab-crash ceiling while a tiled, streaming export stays under the memory budget by processing one chunk at a time

    Stack & engineering · Jun 10, 2026

    Browser memory management: not crashing the tab on a 4K export

    How to keep a heavy in-browser export from crashing the tab: where the memory actually goes (decoded pixels, not file size), why peak usage is what kills you, tiling and streaming so you never hold the whole thing at once, releasing buffers and bitmaps explicitly, and degrading honestly when a device cannot do the job.

    Novus Visualizers

  7. Two swimlanes — a main thread that stays smooth handling UI events and a worker thread doing heavy AI inference — connected by postMessage and a transferred buffer

    Stack & engineering · Jun 9, 2026

    Web Workers and OffscreenCanvas: keeping the UI smooth during heavy AI work

    A practical tour of moving heavy work off the main thread: why a single blocked thread freezes everything, what a Web Worker is and how data crosses to it without being copied, how OffscreenCanvas lets a worker draw directly, and the honest trade-offs in complexity that decide when it is worth doing.

    NSS Background Remover

  8. A blog post represented as a typed code object passing through a type-check gate and a build step into a rendered page, with a struck-through database to signal no CMS

    Stack & engineering · Jun 8, 2026

    Content as code: running a 250-post blog without a CMS

    Why the product blog stores all ~250 posts as typed TypeScript objects instead of in a CMS: the post shape is enforced by the compiler, the whole catalog is versioned and reviewable in git, broken posts cannot ship, and the same tools that build the app build the content — plus an honest account of where this approach stops scaling.

    Novus Stream Solutions (hub)

  9. How we standardized on Claude Code and Claude to build our apps

    Stack & engineering · Jun 7, 2026

    How we standardized on Claude Code to build our apps

    Our path through AI coding tools and LLMs, and why an agentic flow won out for a small business.

    Novus Stream Solutions (hub)

Browse every topic in the resource hub