@itstarun1994 · X

@helloukey · X

@harryjwang · X

I've used many of the major conference systems. Plenty still have docs as an unsearchable static site — or worse, as PDFs that stopped tracking the product three versions ago. Somehow, still true in 2026. We took an AI-first path with instead. Our docs are generated from the codebase itself. A custom Claude Code skill writes each page and retakes the screenshots whenever a feature changes — so the docs don't drift from the product. Every page still gets reviewed by a human before it ships. Now you can talk to them, too. We just shipped "Ask AI" over our docs: This feature also turned out to be a nice teaching case for agentic RAG vs. classic RAG: • Classic RAG: chunk → embed → vector DB → retrieve once, by fixed rules • Agentic RAG: hand the model a search tool and let it drive — write a query, read the results, rewrite, retry At more than 100 pages, still no vector database needed. And every answer cites the exact page it came from. #Age

@AyushGu50073550 · X

Some improvements are still required

@alexander_roese · X

1. Building a platform to help companies capture and preserve critical employee knowledge before it leaves the business. 2. For SMEs that want to reduce knowledge loss, improve onboarding, and make internal expertise easier to access. 3.

u/KangarooPitiful594 · Reddit

I built Aethereum: a team coordinator for AI coding agents (free beta) the simple version: if your team codes with AI agents, aethereum keeps them coordinated so you ship faster. everyone runs whatever agent they like (claude code, cursor, codex, cline, zed) and they all join one room. agents see what each other is building, get warned before breaking each other's changes, and can share code between machines end to end encrypted. when two agents want different API shapes they negotiate it b

@vhm205 · X

Too many news articles, too many bookmarks, too many notes, but I never open them again because I don't know where to find them

Sriram1729 · HN

Tampa, FL | Remote (US Eastern) | Contract, ~20 hrs/week (evenings + weekends, around a full-time job)I'm a full-stack + AI engineer, 5 years in. Looking for one side engagement I can actually commit to — nights and weekends, not a flaky "I'll get to it" thing. Short version of what I'm good for: give me a problem and I'll hand back something deployed. I do the whole thing — backend, frontend, the data model, the infra, the deploy. You don't need to spec it out for me or check my work line by li

@sardamit · X

2-3 years ago, i built the waitlist app for a very popular date place in Mumbai i rebuilt it today using vibe coding

@soracstv · X

I run my AI coding agents with AgentsRoom, a visual command center for multi-agent development. @AgentsRoomDev #VibeCoding #AI

@shawndewet · X

@HiReceptionist · X

AI Receptionist for small businesses