Writing

Engineering notes

RECNOS writes up what we find while auditing and building production systems. Each note is drawn from source code read line by line — including the parts that turned out to be stubs, mocks, or dead code.

Last updated: · By

  • Performance·

    Responsive Images Done Right, and the Rest

    Correct next/image sizing and caching in a production build, alongside dual font loading, a CDN icon dependency, and unoptimised images.

    Read the note
  • Frontend·

    Dead Code in a Shipped Frontend

    An interactive signage subsystem with no importers, a memoised image component nobody uses, and declared dependencies with zero imports.

    Read the note
  • Technical SEO·

    What a File-by-File Code Audit Found

    Structured data, conditional canonicals, sitemap index handlers, and dynamic OG images in a production Next.js marketplace.

    Read the note
  • Backend·

    Geocoding Bad Matches Fail Safely

    A geocoder that rejects partial matches and out-of-bounds coordinates, returning null instead of a plausible wrong location.

    Read the note
  • Technical SEO·

    Gating Programmatic Pages on Real Inventory

    How a Bangalore PG marketplace publishes locality and intent pages only when the underlying listing count justifies them, and canonicalises the rest.

    Read the note