Launch HN: Haystack (YC W21) – Engineering analytics that don’t suck

1

Haystack Analytics

Heads up: site is not loading. Ios Safari & macOS Chrome.<p>Mixed Content: The page at '<a href="https://usehaystack.io/" rel="nofollow">https://usehaystack.io/</a>' was loaded over HTTPS, but requested an insecure favicon '<a href="http://www.usehaystack.io/favicon.ico" rel="nofollow">http://www.usehaystack.io/favicon.ico</a>'. This request has been blocked; the content must be served over HTTPS.

#Data Dashboard #Software Engineering #Predictive Analytics 2 social mentions

2

LayerCI

Hey, this looks really cool.<p>In my line of work [1] I talk to a lot of developers about productivity, here are some questions about what you've built in the context of that experience:<p>1. I think "number of commits" or "number of pull requests" merged are proxies for productivity at best. Most teams that I've seen care more about "are the tasks for the epic being chipped down" - is that something your tool can help estimate as well? The progress bar for the epic? It'd be nice to get a table of the metrics and where they come from.<p>2. In the same vein, "scrum with epics" might not always be how teams decide on units of work, do you support other methodologies?<p>3. You mention deployment frequency a lot, but that seems tangent to developer productivity - Isn't getting things deployed quickly mostly for the benefit of the product folks? (getting feedback faster)<p>4. How does maintenance work fit into this? Does a developer who spends most of their time refactoring show up with "worse metrics" than someone pushing copy changes to the landing page?<p>[1] CEO @ <a href="https://layerci.com" rel="nofollow">https://layerci.com</a> (YC S20).

#Continuous Integration #Continuous Deployment #DevOps Tools 3 social mentions