15:[[47300047,{"by":"shoman3003","descendants":11,"id":47300047,"kids":[47302074,47303558,47310681,47315154,47312814,47301473,47300562],"score":12,"text":"$16","time":1772996545,"title":"OpenAI might end up on the right side of history","type":"story"}],[47197861,{"by":"plsft","descendants":4,"id":47197861,"kids":[47198316,47198029],"score":4,"text":"NuGet's default registry is serviceable, but discovering and comparing packages isn't great.

nugx.org (http://nugx.org/) is an alternative front-end with better search, popularity signals, dependency graphs, and a cleaner UI.

Built with Noundry (C# packages/tooling). Currently in beta — would love feedback on nugx.org.

nugx.org (https://nugx.org/)","time":1772299427,"title":"Show HN: Nugx.org – A Fresh Nuget Experience","type":"story","url":"https://nugx.org"}],[47127532,{"by":"dmpyatyi","descendants":19,"id":47127532,"kids":[47130259,47131455,47133537,47131706,47127588,47132401,47127552,47131925,47180079,47140387,47135969,47129690,47135355,47134099,47128663],"score":38,"text":"YC recently put out a video about the agent economy - the idea that \nagents are becoming autonomous economic actors, choosing tools and \nservices without human input.

It got me thinking: how do you actually optimize for agent discovery? \nWith humans you can do SEO, copywriting, word of mouth. But an agent \njust looks at available tools in context and picks one based on the \ndescription, schema, examples.

Has anyone experimented with this? Does better documentation \nmeasurably increase how often agents call your tool? Does the \nwording of your tool description matter across different models \n(ZLM vs Claude vs Gemini)?","time":1771875121,"title":"Ask HN: How do you know if AI agents will choose your tool?","type":"story"}],[47105306,{"by":"GoatPerfect","descendants":6,"id":47105306,"kids":[47105458,47106012,47105433],"score":4,"text":"I’ve been working on a project where webhooks are a core part of the system, and I realized how fragile they can be in practice.

Transient network errors, timeouts, downstream issues — things fail more often than expected.

I’m curious how others are handling this in production.

Are you building custom retry logic?

Using a queue?

Relying on provider retries?

Just logging and manually checking failures?

Do you monitor webhook delivery rates or alert on repeated failures?

Would love to hear what setups people are using and what’s worked (or not worked) for you.","time":1771711430,"title":"Ask HN: How do you monitor and retry failed webhooks in production?","type":"story"}],[47105542,{"by":"SoundsDebatable","descendants":5,"id":47105542,"kids":[47105937,47105575,47105587],"score":2,"text":"What’s the biggest honor someone in tech can receive that isn’t money, a job title, or company success?

Is it being inducted into a Hall of Fame like the Internet Hall of Fame?

Winning a major industry award from groups like ACM?

Being profiled by top outlets such as Wired or TechCrunch?

Or is it something less formal — like earning deep respect from peers and being cited as an inspiration by other builders?

What do you think is the highest non-financial honor in tech?","time":1771713093,"title":"Ask HN: What Matters Most in Tech? Awards, Media Praise, or Peer Respect","type":"story"}]]

user:	JacobArthurs
created:	February 21, 2026
karma:	1
about:	https://JacobArthurs.com https://github.com/jacobarthurs https://blog.jacobarthurs.com