João Moreira · Front-end & Full Stack DeveloperSoftware,end to end.

It brings a SQL editor with Vim mode and live diagnostics, a results grid, a command palette, schema diff, EXPLAIN plans drawn as trees, import, export and backup, plus connections over TLS, SSH tunnels and proxies. A DELETE without WHERE on production only runs after typing the connection's name, read-only connections are enforced on the server too, and AI agents only write through approved, timed grants. It is local-first with no telemetry, and ships through Homebrew, Scoop, the AUR, .deb/.rpm packages and a Windows installer.

It covers catalogs and variations, cart, delivery, real-time orders, customers, business hours, cash flow, accounts, purchasing, inventory, suppliers and staff. The Rust API centralizes authentication, multi-tenant rules, auditing, rate limiting, files and integrations; local modules keep checkout and printing close to daily operations.

The PWA/Capacitor client keeps a local operation queue with synchronization, conflict and quota states. A Rust/Axum backend coordinates PostgreSQL, SeaORM, S3 files and OpenAPI; a separate master app manages companies, plans, billing, storage and auditing without exposing each tenant's agronomic data.

Route Handlers keep Supabase credentials on the server, validate uploads and normalize voter names. Database constraints, rate limiting and time-window checks reinforce the public flow without an unnecessary admin panel.

The server calculates pricing and capacity, generates a BR Code with CRC16 and stores receipts in a private bucket. The admin area brings together orders, attendees, tiers, check-in, receipts, status, notes and CSV exports.

The agent rewrites a complete draft on every turn, transcribes audio, validates cities and seed varieties against hybrid BM25/fuzzy catalogs, persists conversations and collections, and tracks delivery and follow-ups. FastAPI and PostgreSQL provide auditing and continuity.

Reports consolidate finances, ROI and profit allocation. Server Actions, Zod validation, resource/action permissions and PostgreSQL RLS policies protect operations and documents per user.

Each challenge explains the concept, uses analogies, provides reproducible steps and validates a flag. Progress stays in the browser, with four levels separating fundamentals, inspection, controlled mutations and sessions.

The Rust/Tauri architecture uses mDNS discovery, QUIC with TLS and Ed25519 identities, Win32 capture/injection and a bilingual React/Mantine UI. Its internal lab exposes probes and input-pipeline metrics for diagnosing real hardware.

The work explored image augmentation, bite/idle classification with YOLOv8, PyTorch/CUDA training, screen-region capture and real-time inference with thresholds, consecutive frames and cooldown. It was built only for learning and is archived; automation must respect the game's terms.

Machines, splitters, mergers, storage, text and frames form interactive graphs. Magic Planner builds production chains automatically; projects can be saved, published, forked and exported using data extracted from the game's official documentation.

BrightScript tasks load and normalize categories, artwork, plots, ratings, genres and URLs into SceneGraph ContentNodes, distinguishing movies from series while keeping network work off the UI thread.

The Rust backend proxies the official API, selects compatible releases and powers a persistent queue with pause, HTTP Range resume, progress and stall detection. Profiles isolate mods and configuration, using Windows junctions for activation and game launching.

CO, NO₂, SO₂ and PM2.5 sensors connect ESP32 and SX1278/LoRa radios to a gateway and React interface. The demo includes indicators, time series, devices and reports; some data remains simulated because this is a hackathon prototype.