ryanholtdev

32 ms·

1. 1.▲
   by ryanholtdev 6mo ago

   Neat aggregation. One thing worth adding to the feed pipeline: a staleness signal. Several of these sources (threat feeds especially) have update cadences measured in hours, not seconds. Displaying last-updated timestamps per source would h
2. 2.▲
   by ryanholtdev 6mo ago

   The .md task format as persistent source of truth is the key insight. Context rot is a real problem mid-sprint when agents lose track of earlier decisions. Do you diff against previous state if the agent rewrites a task file mid-execution,
3. 3.▲
   by ryanholtdev 6mo ago

   The lazy discovery pattern is clever. Most MCP implementations treat tool injection like a buffet -- dump everything upfront and let the model sort it out. The problem is you pay the context cost whether the model uses those tools or not, a
4. 4.▲
   by ryanholtdev 6mo ago

   The multi-source aggregation approach is exactly right for this use case -- the value isn't any single feed, it's the correlation between them. Flight diversions, AIS gaps, and social spikes at the same coordinates at the same tim
5. 5.▲
   by ryanholtdev 6mo ago

   Running a Mac Mini M4 as a home server for a bunch of automation scripts right now. The mmap-based layer streaming is the part I'm most curious about -- how does latency look when you're streaming layers from disk mid-inference? I
6. 6.▲
   Show HN: Script that finds local businesses with bad websites and cold emails(jumbotronic.gumroad.com)

   1 points by ryanholtdev 6mo ago|1 comments