reactiverobot
Joined 10 years ago
Karma
44
Submissions
34
Member since
Mar 24
Recent submissions
Comment · 2 months ago
Comment · 2 months ago
haha that visual is perfect
Comment · 2 months ago
thank you! yeah it's all about the right balance :D
Comment · 2 months ago
Hi everyone, I’m Matt, founder of Ref (https://ref.tools). Ref is the shared workspace where engineering teams align on what agents should build before code gets written.
Every engineering team is battling the same problem. We call it Velocity Sickness. It's the disconcerting feeling that you're moving fast but not having the impact you expect. It's affecting individuals, teams and especially leaders.
It looks like: - Too many PRs to merge. - Brainfry and burnout. - Engineers running in different directions. - Critical decisions being made by agents.
The last one is the most dangerous. At its core, software engineering is about two things: (1) what decisions matter for my system? and (2) making those decisions. When you let agents make critical decisions, you lose ownership of your system and product.
You solve these problems with Ref.
The art of modern software engineering is balancing pre-work vs re-work.
Our existing tools jump us straight into implementation and re-work. Ref is a tool for the decision layer and works with all your existing implementation tools and agents.
And because this is hackernews, I want to be super clear: I am NOT saying “never read the code”. Not yet, anyways.
Comment · 1 year ago
ref-tools-mcp is similar and does support openai's deep research spec
Comment · 1 year ago
Hi! I'm the developer of Ref (https://ref.tools), the MCP server for giving coding agents access to public and private docs. Ref's goal is to provide exactly the tokens you need to guide the model and nothing else.
I've been working on this one MCP server for about 6 months and I wanted to share the ways I've used and considered using different MCP features. If you're new to MCP, I hope this article can give you a sense of how developers can leverage MCP in practice.
Repo: https://github.com/ref-tools/ref-tools-mcp
And because I get asked this ALL the time : how is Ref different from Context7? - Ref uses on avg 55% fewer tokens with the same or better accuracy (eval blog post: https://ref.tools/blog/how-make-search-good) - Ref allows indexing your own private github repos and pdfs - Ref is a paid product with 200 free searches to start
I appreciate you taking a look!
first I jot down my notes then I work with one agent to write a plan. this is just the first draft.
Once I have a draft, I start to leave comments to ask questions and launch multiple agents to research and refine parts of the plan.
(optionally share the plan with my team for feedback)
then have multiple agents work on implementing parts of the plan
Ref is great for this because it can orchestrate agents and you can track all the progress on one place. It's hosted so you just work from a browser like Google Docs but can connect to local agents too