Show HN: Zero Browser
Data driven browser system Comments URL: https://news.ycombinator.com/item?id=48548406 Points: 3 # Comments: 0
Insights
Engineering perspectives on architecture, product development, AI, and the everyday decisions behind useful software.
From the engineering desk
Browse practical articles or follow the latest technology updates.
Subscribe via RSS →Curated links from external sources — not 360Softy original articles.
Data driven browser system Comments URL: https://news.ycombinator.com/item?id=48548406 Points: 3 # Comments: 0
Most AI coding assistants are glorified autocomplete on steroids. They suggest code, maybe write a function or two, but leave you holding the bag when it comes to testing, verification, and actually shipping the changes. M31A (M31 Autonomous) takes a different approach. It's a terminal-based AI coding agent written in Go that owns a six-phase workflow end-to-end: Initialize → Discuss → Plan → Execute → Verify → Ship. Every run ends with a verified git commit and a learning ledger entry. One sta
Supabase Authentication & Authorization Patterns Authentication and authorization are the foundation of secure applications. Supabase provides a complete auth system with email/password, social logins, magic links, and powerful row-level security. This guide covers everything you need to build secure, production-ready authentication. Built-in Features: Email/password authentication Social OAuth providers (Google, GitHub, etc.) Magic link (passwordless) authentication Multi-factor authenticatio
Your Trending Repos Script Broke. Again. You set up a GitHub Action to scrape trending TypeScript repos. It ran at 9 AM. You got an empty JSON array. No errors. Just []. Sound familiar? Here's what happened: GitHub's trending page changed its HTML structure. Your cheerio selector stopped matching. The cron job ran happily, found zero repos, and overwrote your daily digest with nothing. Nobody noticed until someone asked "why wasn't X trending yesterday?" This sucks. I know. I've debugged this
Every RAG app and agent eventually hits the same wall: you have more stuff than fits in the model's context window — a system prompt, chat history, retrieved documents, tool output — and a fixed token budget. The usual "fix" is to truncate the whole blob at the end. Which means you randomly chop off whatever happened to be last: sometimes a doc, sometimes half your system prompt. You drop the wrong things. I got tired of rewriting that logic in every project, so I built contextcram — a tiny, zer
When people imagine freelancing, they usually picture freedom. Flexible schedule. Working for yourself. Laptop life. Coffee shop mythologies. The usual propaganda. What they do not picture is the mental load. That was one of the first things that hit me once I started doing real freelance work. The coding matters, obviously. But the part that wears you down is not always the code itself. It is trying to hold the entire project in your head at once. What did I finish last time? What broke when I
The worst place to look for your first app idea is nowhere. That sounds obvious, but it is what a lot of people do. They sit down, open a notebook, stare into the middle distance, and ask: "What app should I build?" That question is enormous. It is too big. It has no walls. It gives your brain nothing to grab. It is like asking, "What should I do with my life?" while standing in front of a vending machine. No wonder people freeze. Then they do the next predictable thing. They start thinking in g
If Cursor rules aren't working, you're not alone. You wrote .cursor/rules (or a legacy .cursorrules file) telling the agent to use named exports, Zod validation, and your error-handling pattern — and the agent still generates default exports and skips validation. This usually means one of three things: The rules file is in the wrong place or format The rules are too vague for the model to prioritize The conventions you wrote don't match what your team actually enforces in PR review Cursor rules
Let’s start with a conversation
An idea, a challenge, or a system that needs to work better. We’ll help you understand the next step.
Prefer email? [email protected]