Skip to content
SiftSift

About

Sift is built and maintained by Sérgio Cardoso, a Senior Software Engineer based in São Paulo, Brazil, with over 20 years of experience building software in production.

Background

Section titled “Background”

Sérgio’s career spans two decades: from webcasting and live-streaming infrastructure (FFmpeg, encoding, transcoding, VOD) at TVAOVIVO, to corporate dashboards and risk/credit analysis tools at Boa Nota, to editorial products, legal-data pipelines, and AI automation at JOTA, where he’s worked since 2021 — moving from frontend into full-stack engineering, data pipelines, and applied AI.

His current focus sits at the intersection of software engineering, product, and applied AI: agent-assisted engineering and specification-driven development — turning business problems into architecture, context, acceptance criteria, and a working system, while retaining direct technical ownership of code quality, observability, and production operations.

Stack

Section titled “Stack”

React, Next.js, TypeScript, Python, Node.js, PostgreSQL, Flutter, n8n, Docker, GCP, FFmpeg, Whisper, and AI/LLM tooling (agents, RAG, embeddings, vector databases, local models) — Sift’s own choices (Rust, no mandatory network access, no mandatory AI) reflect the same engineering instinct: pragmatic, production-grade, and unafraid to say no to unnecessary complexity.

Other work

Section titled “Other work”

Beyond client and employer work, Sérgio ships his own products end to end — Precivo (cost/pricing for makers, Flutter), Healthy Chew (mindful eating, Flutter), Caminho Solo (earnings tracking for gig drivers), Cancelo (free-trial reminders, React Native/Expo), and Alerta Edital (AI-driven government procurement monitoring), among others — listed with links on sergiocardoso.dev. Sift itself is an open-source project out of Flokin, his lab for independent products and experimentation.

Elsewhere

Section titled “Elsewhere”
Section titled “Related”
  • Contributing — how to propose changes to Sift.
  • Security — how to reach the maintainer about a vulnerability specifically.