For humans - more documentation is bad. Simple documentation is generally better.
For AI - what type of documentation is better? Is code + RAG sufficient? Do we need more text format summaries?
Haystack (YC W21) | Remote | Full-time | usehaystack.io
Haystack helps dev teams get incredibly good at delivering software. We do that using analytics and alerts pulled straight from Github.
Haystack is a fast growing early startup. From 0 to 1.5 years companies like Microsoft, The Economist, Cameo, Indiegogo and many more are using Haystack daily!
Haystack helps dev teams get incredibly good at delivering software. We do that using analytics and alerts pulled straight from Github.
Haystack is a fast growing early startup. From 0 to 1.5 years companies like Microsoft, The Economist, Cameo, Indiegogo and many more are using Haystack daily!
Haystack helps dev teams get incredibly good at delivering software. We do that using analytics and alerts pulled straight from Github.
Haystack is a fast growing early startup. From 0 to 1.5 years companies like Microsoft, The Economist, Cameo, Indiegogo and many more are using Haystack daily!
Your marketing demo had a facebook ads source but when I installed the add-on, I couldn't find a way to connect my own facebook ads account anywhere. How can I do this?
You're right. It's not available at the moment but we are launching Facebook Ads integration very soon! Are there any other marketing sources like Facebook Ads you would like to see?
The product focuses on giving visibility by visualizing trends, identifing blockers and optimizing code reviews.
As long as the team has a visibility problem Haystack should be beneficial.
We have organizations prefering to use the stats more privately and only mention the necessary stats to engineers. We also have organization using our product in their daily standups. It depends on how the team choses to use it. We have seen both styles work well.
What is the purpose of this particular approach?