Live data from Hacker News

Launch HN: Dart (YC W22) – Project management with automatic report generation

news.ycombinator.com

61–70 of 76 posts

Re: Launch HN: Dart (YC W22) – Project management with automatic report generation

#63
post #6

Was it a deliberate decision to go with a name that clashes with a top 20 programming language?

Even as a dev I hadn't really thought about it clashing with a programming language, therefore I doubt most other people would care

I couldn't understand why Google was launching a Dart startup.

Re: Launch HN: Dart (YC W22) – Project management with automatic report generation

#64

I think project mgmt software suffers from the same problem as project managers - they think they should be in charge, visible and front and centre I disagree (esp about the human ones) I want project management that fills itself in based on work people do, not work people tell the tool they have done. I am dubious that putting ticket numbers in commit messages is needed - let alone IRC, emails, phone calls meetings,…

Spot on, hopefully apps like these can reduce the number of and/or completely replace overbearing PMs.

Re: Launch HN: Dart (YC W22) – Project management with automatic report generation

#65
post #62

Great pricing model when compared with Linear.app. If I have a budget of $8 I’d love to subscribe Dart rather than Linear.app

What's the difference to Linear? The only difference I could see is the $2/month cheaper pricing on the largest plan.

Re: Launch HN: Dart (YC W22) – Project management with automatic report generation

#68

Best project management tool, IMO, is the tool that has no projects to manage. We tried JIRA, Linear, now we are using Github projects. It is too much effort to keep it up to date when things are fast moving. Everything becomes stale. At first look, it feels like this too will suffer the same. The best tool in this space should eliminate the need of specialized PM. PS. Github project has become surprising better in r…

Also had a good exp at my last startup using GitHub projects. Very dev driven/dev friendly. Easy to highlight over-work, easy to have multiple views (sectioned lists for prioritization, columns for limiting WIP) There’s a decent parent/child relationship for splitting up large tasks across hands (though I try to avoid this). Dart looks interesting, but give GH projects a whirl

Re: Launch HN: Dart (YC W22) – Project management with automatic report generation

#69
post #19

Looks interesting. Does it do progress forecasting based on historical task velocity, without the need for manual estimation? (See eg: https://screenful.com ) Ed: Does it support importing historical data, and/or external data sources like GitHub, Jira, Trello etc - for current projects and to set a baseline grounded in data? Like historical velocity? Ed2: I guess so? From the welcome email: > Once you're logged in,…

>> progress forecasting based on historical task velocity, without the need for manual estimation? Yeah give managers another topic for quick one-hour weekly sessions )))

I'd rather have one hour/week, triaging milestones based on data-driven estimation with confidence intervals than an hour a day of planning poker ...

Re: Launch HN: Dart (YC W22) – Project management with automatic report generation

#70
post #49
post #45

Earlier quoted context omitted.

Regarding embeddings - I am assuming you are using ada-002 or have you moved on to 3-small already? Do you have a particular strategy for migrating embedding models other than re-embed the whole dataset? And lastly, what is/are your vector store(s) of choice? I am not quite sure of your scale but I have found that north of 50 million vectors a lot of the current options get a bit weak in the knees, especially if you…

- Still on ada-002, planning on migrating later this week actually - Current plan is to re-embed everything but I'm very open to better ideas there haha. Is there a better way? - I've heard some similar stuff but we haven't run into it yet. What are you working with?

One strategy is to store the model version used for each vector, and then using the appropriate model to embed your queries. Of course that means that for a certain time frame you may need to blend two result sets, so that may not be ideal for your use case. You could also choose to just re-embed the last 90 days or so, or in your case on a project by project basis. Of course all of this raises your search complexity because you need to track your model versions.

From a vector store side we have worked with Weaviate, Qdrant, Pinecone, Milvus, and Elasticsearch. All of them had their pros and cons, and none of them were as stable as we liked once you really went to scale. Cloud deployments were rather pricey as well at that volume. We ended up with a mix of Qdrant Weaviate and Elastic for different workloads.

Post reply on HN