frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

NewASM Virtual Machine

https://github.com/bracesoftware/newasm
1•DEntisT_•1m ago•0 comments

Terminal-Bench 2.0 Leaderboard

https://www.tbench.ai/leaderboard/terminal-bench/2.0
1•tosh•1m ago•0 comments

I vibe coded a BBS bank with a real working ledger

https://mini-ledger.exe.xyz/
1•simonvc•1m ago•1 comments

The Path to Mojo 1.0

https://www.modular.com/blog/the-path-to-mojo-1-0
1•tosh•4m ago•0 comments

Show HN: I'm 75, building an OSS Virtual Protest Protocol for digital activism

https://github.com/voice-of-japan/Virtual-Protest-Protocol/blob/main/README.md
3•sakanakana00•7m ago•0 comments

Show HN: I built Divvy to split restaurant bills from a photo

https://divvyai.app/
3•pieterdy•10m ago•0 comments

Hot Reloading in Rust? Subsecond and Dioxus to the Rescue

https://codethoughts.io/posts/2026-02-07-rust-hot-reloading/
3•Tehnix•10m ago•1 comments

Skim – vibe review your PRs

https://github.com/Haizzz/skim
2•haizzz•12m ago•1 comments

Show HN: Open-source AI assistant for interview reasoning

https://github.com/evinjohnn/natively-cluely-ai-assistant
3•Nive11•12m ago•4 comments

Tech Edge: A Living Playbook for America's Technology Long Game

https://csis-website-prod.s3.amazonaws.com/s3fs-public/2026-01/260120_EST_Tech_Edge_0.pdf?Version...
2•hunglee2•16m ago•0 comments

Golden Cross vs. Death Cross: Crypto Trading Guide

https://chartscout.io/golden-cross-vs-death-cross-crypto-trading-guide
2•chartscout•18m ago•0 comments

Hoot: Scheme on WebAssembly

https://www.spritely.institute/hoot/
3•AlexeyBrin•21m ago•0 comments

What the longevity experts don't tell you

https://machielreyneke.com/blog/longevity-lessons/
2•machielrey•22m ago•1 comments

Monzo wrongly denied refunds to fraud and scam victims

https://www.theguardian.com/money/2026/feb/07/monzo-natwest-hsbc-refunds-fraud-scam-fos-ombudsman
3•tablets•27m ago•1 comments

They were drawn to Korea with dreams of K-pop stardom – but then let down

https://www.bbc.com/news/articles/cvgnq9rwyqno
2•breve•29m ago•0 comments

Show HN: AI-Powered Merchant Intelligence

https://nodee.co
1•jjkirsch•32m ago•0 comments

Bash parallel tasks and error handling

https://github.com/themattrix/bash-concurrent
2•pastage•32m ago•0 comments

Let's compile Quake like it's 1997

https://fabiensanglard.net/compile_like_1997/index.html
2•billiob•33m ago•0 comments

Reverse Engineering Medium.com's Editor: How Copy, Paste, and Images Work

https://app.writtte.com/read/gP0H6W5
2•birdculture•38m ago•0 comments

Go 1.22, SQLite, and Next.js: The "Boring" Back End

https://mohammedeabdelaziz.github.io/articles/go-next-pt-2
1•mohammede•44m ago•0 comments

Laibach the Whistleblowers [video]

https://www.youtube.com/watch?v=c6Mx2mxpaCY
1•KnuthIsGod•45m ago•1 comments

Slop News - The Front Page right now but it's only Slop

https://slop-news.pages.dev/slop-news
1•keepamovin•50m ago•1 comments

Economists vs. Technologists on AI

https://ideasindevelopment.substack.com/p/economists-vs-technologists-on-ai
1•econlmics•52m ago•0 comments

Life at the Edge

https://asadk.com/p/edge
4•tosh•58m ago•0 comments

RISC-V Vector Primer

https://github.com/simplex-micro/riscv-vector-primer/blob/main/index.md
4•oxxoxoxooo•1h ago•1 comments

Show HN: Invoxo – Invoicing with automatic EU VAT for cross-border services

2•InvoxoEU•1h ago•0 comments

A Tale of Two Standards, POSIX and Win32 (2005)

https://www.samba.org/samba/news/articles/low_point/tale_two_stds_os2.html
4•goranmoomin•1h ago•0 comments

Ask HN: Is the Downfall of SaaS Started?

4•throwaw12•1h ago•0 comments

Flirt: The Native Backend

https://blog.buenzli.dev/flirt-native-backend/
3•senekor•1h ago•0 comments

OpenAI's Latest Platform Targets Enterprise Customers

https://aibusiness.com/agentic-ai/openai-s-latest-platform-targets-enterprise-customers
2•myk-e•1h ago•0 comments
Open in hackernews

Show HN: I built an open-source AI data layer that connects any LLM to any data

https://github.com/bagofwords1/bagofwords
18•y14•4mo ago
Excited to share a project I’ve been building for months! Would love to receive honest feedback :)

My motivation: AI is clearly going to be the interface for data. But earlier attempts (text-to-SQL, etc.) fell short — they treated it like magic. The space has matured: teams now realize that AI + data needs structure, context, and rules. So I built a product to help teams deliver “chat with data” solutions fast with full control and observability (agent tracing, quality scores, etc) — am I wrong?

The product allows you to connect any LLM to any data source with centralized context (instructions, dbt, code, AGENTS.md, Tableau) and governance. Users can chat with their data to build charts, dashboards, and scheduled reports — all via an agentic, observable loop. With slack integration as well!

* Centralize context management: instructions + external sources (dbt, Tableau, code, AGENTS.md), and self-learning

* Agentic workflows (ReAct loops): reasoning, tool use, reflection

* Generate visuals, dashboards, scheduled reports via chat/commands

* Quality, accuracy, and performance scoring (llm judges) to ensure reliability

* Advanced access & governance: RBAC, SSO/OIDC, audit logs, rule enforcement

* Deploy in your environment (Docker, Kubernetes, VPC) — full control over infrastructure

GitHub: github.com/bagofwords1/bagofwords

Docs / architecture / quickstart: docs.bagofwords.com

Comments

y14•4mo ago
The hardest problems building this weren’t in the LLM logic, but in everything around it —-observability, access control, and managing context across dbt, Tableau, and code. Finding the balance between a strict semantic layer and LLM agency was tricky. Too rigid and it loses llm magic, too loose and reliability breaks

What worked for me and my users was leaning on instructions + AGENTS.md + metadata as a lighter abstraction layer — structured enough for trust, but flexible enough to keep the model useful.

If you’ve been exploring similar ideas or trying to productionize AI analysts, I’d love to hear how you’re approaching it

ddmdd•4mo ago
how do you make sure there's no context bloat?
y14•4mo ago
Thanks for the question. Avoiding context bloat and overall engineering the context is (still) most of work. What’s been working:

- Role scoped calls: data modeling, code gen, are separate calls where each gets its own tailored context

- Context is divided into sections (tables, dbt, instructions, code) and each is getting a hard limit budget (required some experimentation, liked Cursor’s priompt project)

- agentic retrieval: agents can call tools to fetch or search data/metadata when needed

- summaries for different objects: messages, widgets; reports, data samples/profiles.

I wrote some more about how the agent and context work in the docs