reactiverobot
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
How I design with AI as an engineer who is not a designer and hates slop
AI Broke Code Review and It's Breaking Your Team
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.
Things I said as a manager part 6: Leveling up hurts
Show HN: Simple visual tools for common situations in your LLM via mcp-UI
https://github.com/ref-tools/widget-mcp
MCP-UI is super early but I'm pretty excited about the idea of LLM chat interfaces no longer being a wall of text and including visual elements.The ceiling of what mcp-ui enables is super high since it can really be anything but that makes it hard to imagine.To me, considering the floor of what mcp-ui offers is much more compelling. It lets us plug a gap where Google search beats LLM chat - the...
Show HN: Todo.md
I'm full-time developer and wanted to try vibe coding so I made this with Figma Make.
Things I said as a manager part 4: Only outcomes matter
Things I said as a manager part 4: Always be pitching
Pieces of Autonomy
Ref uses MCP to build documentation search that minimizes token use
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!
Also FYI a bunch of search quality improvements dropped this week so you might want to try again. :)
I'm surprised you took away from this that I think the goal should be making more humans because that's not what I believe and not what was I was trying to communicate. I don't think there is one "goal" to life and this article was in now way about goals but I'm glad you have such a sense of purpose for your life! I wish you well in that too!
Just because you mention it though - its a false dichotomy that creating more lives is at odds with improving the lives of the current existing people.
Legacy
Things I said as a manager part 3: Code review is your job
Fortunately, that didn't happen in this case. Part of building a team is getting to know talented people before they're looking for a job so when they're ready they reach out to you.
And you're right, this is work, not dating. But that doesn't remove the human emotion involved in getting to know someone.
The candidate and I first met long before they were interested in interviewing. They had potential and I got to know them so that when they were interested in interviewing they'd reach out. Once they decided to interview, we made that happen as quickly as schedules allowed!
Hope that clarification helps! Thanks for the note!
Can you share a little more about what made the decision emotional or impulsive? I'd love to make sure my writing is clear and it sounds like it wasn't. While building a relationship with a candidate can be emotional, we always use a standardized rubric to evaluate candidates. Even with a rubric the decisions can be hard!
Thanks for the note!
Thanks for the note!
I obviously can't go into the details of the feedback but I share your wish that hiring decisions would more cut and dry! It would be a lot easier for everyone.
Thanks for the feedback!
As a hiring manager you do cold out reach and meet people well before they are ready to look for a new job. You build a relationship over time so that when they are ready for a new job they reach out to you. That's what happened in this case.
I appreciate the feedback that I was not clear about that. I agree with you all that spending months actually interviewing is horrendous and unfair.
Let me know if you have more questions or thoughts!