Show HN: Building a SQL analyst agent from scratch https://ift.tt/q8CcXSF

Show HN: Building a SQL analyst agent from scratch I built a SQL analyst agent based on a simple idea: generating SQL is not the same as doing analysis. Most text-to-SQL tools stop at producing a query. But real analysis is iterative. You explore the schema, run queries, adjust, and refine. This project tries to model that loop instead of treating a query as the final output. I wrote about the approach, challenges, and tradeoffs here: https://ift.tt/Un8Mtgu Github repo: https://ift.tt/0IBrL9Q https://ift.tt/Un8Mtgu April 26, 2026 at 11:07PM

Show HN: I remade my blog into a Windows 3.1 environment https://ift.tt/tYAwmVe

Show HN: I remade my blog into a Windows 3.1 environment https://passo.uno/ April 26, 2026 at 01:02AM

Show HN: Implit – Catch fake AI-generated dependencies https://ift.tt/hbG3gRC

Show HN: Implit – Catch fake AI-generated dependencies https://ift.tt/iAaomb3 April 25, 2026 at 07:49PM

Show HN: Odozi – open-source iOS journaling app https://ift.tt/0g6TSyF

Show HN: Odozi – open-source iOS journaling app Yeah I know I hate the name too but I wasn't about to pay up for odyssey.app. It's an open source project so feel free to poke around with it / fork it. I talk about it more on the marketing website, but a few of us have been using it for the past month and kind of fun. Obviously there will be a slew of issues / feedback / nits that come from this, but c'est la vie. GH is here: https://ift.tt/ABm1ych https://odozi.app April 25, 2026 at 05:52AM

Show HN: Quay – Menu-bar Git sync https://ift.tt/WoIrsLa

Show HN: Quay – Menu-bar Git sync I write Astro blog posts in a text editor; when I'm done I want them pushed to GitHub so Cloudflare deploys the site. To make it comfortable, I built Quay for the menu bar. Also useful for Obsidian vault syncing. Point it at a folder, connect a GitHub repo, and it stages/commits/pushes/pulls. Multiple repos, editable commit messages, branch switching, merges with conflict detection. Shows open issue and PR counts per repo. But it's is not a full Git client (no diffs, blame, cherry-pick, or rebase) and it doesn't create remote repos. Native macOS app (Swift/SwiftUI). Wraps the local git binary (prompts to install Xcode Command Line Tools if missing). No custom Git implementation. Sandboxed, no telemetry, GitHub-only. macOS. 7-day trial, €9 one-time on the App Store. https://ift.tt/ARmFyOz April 25, 2026 at 08:23AM

Show HN: SherifDB, a databe written in Golang under 500 LOC https://ift.tt/8EozZTa

Show HN: SherifDB, a databe written in Golang under 500 LOC https://emmanuel326.github.io/blogs/sheriffdb.html April 25, 2026 at 04:42AM

Show HN: WhiskeySour – A 10x faster drop-in replacement for BeautifulSoup https://ift.tt/SHioP71

Show HN: WhiskeySour – A 10x faster drop-in replacement for BeautifulSoup The Problem I’ve been using BeautifulSoup for sometime. It’s the standard for ease-of-use in Python scraping, but it almost always becomes the performance bottleneck when processing large-scale datasets. Parsing complex or massive HTML trees in Python typically suffers from high memory allocation costs and the overhead of the Python object model during tree traversal. In my production scraping workloads, the parser was consuming more CPU cycles than the network I/O. Lxml is fast but again uses up a lot of memory when processing large documents and has can cause trouble with malformed HTML. The Solution I wanted to keep the API compatibility that makes BS4 great, but eliminates the overhead that slows down high-volume pipelines. It also uses html5ever which That’s why I built WhiskeySour. And yes… I *vibe coded the whole thing*. WhiskeySour is a drop-in replacement. You should be able to swap from "bs4 import BeautifulSoup" with "from whiskeysour import WhiskeySour" and see immediate speedups. Your workflows that used to take more than 30 mins might take less than 5 mins now. I have shared the detailed architecture of the library here: https://the-pro.github.io/whiskeySour/architecture/ Here is the benchmark report against bs4 with html.parser: https://the-pro.github.io/whiskeySour/bench-report/ Here is the link to the repo: https://ift.tt/nCf50DS Why I’m sharing this I’m looking for feedback from the community on two fronts: 1. Edge cases: If you have particularly messy or malformed HTML that BS4 handles well, I’d love to know if WhiskeySour encounters any regressions. 2. Benchmarks: If you are running high-volume parsers, I’d appreciate it if you could run a test on your own datasets and share the results. April 25, 2026 at 04:23AM