Is something like this always just a hack/shortcut or are there people who want this as their ideal workflow?
Is something like this always just a hack/shortcut or are there people who want this as their ideal workflow? I'm curious because I see stuff like this all the time being submitted to YC. For example, is this for IT / DBAs that need to gather info for data analysts, marketers and sales people? Are there many people in that position and what would the ideal flow look like? I can see startups and small companies willing to use this as a stopgap, but I couldn't imagine larger customers/companies willing to use something like this. This isn't to say I don't know why this was built. The same forces are what drove us to build Wufoo. We were tired of building these tedious data collection apps. The DIY builder was out of laziness on our part. But when it comes to accessing existing data, there's so many concerns about security and privacy that I worry an idea like this will always be limited in terms of adoption. If people think differently, I would love to know.
Posted by kevin on Jun 19, 2015, 9:59 PM
Tags
Related issues
- The biggest problem with having an LLM do this, from what I've observed of at least frontier models, is that the way they are trained...
- The biggest problem with MOND is that it was hand-crafted with additional parameters simply to fit the data.
- (My comment is about detached houses).
- The biggest problem with this is that I can't run my company's own internal benchmarks against this API, because they will be trained int...
- > steer Claude away from over-engineering parts of the system in response to hypothetical concerns.
- Why is there no comparison with FLUX 3 Image?
Raise real-world problems, find people facing the same issue, and discuss solutions.6,000 issues0 comments
hackernews (Other)
The biggest problem with having an LLM do this, from what I've observed of at least frontier models, is that the way they are trained...
The biggest problem with MOND is that it was hand-crafted with additional parameters simply to fit the data.
(My comment is about detached houses).
The biggest problem with this is that I can't run my company's own internal benchmarks against this API, because they will be trained int...
> steer Claude away from over-engineering parts of the system in response to hypothetical concerns.
Why is there no comparison with FLUX 3 Image?
> our Git monorepo was developing an annoying problem Sentences like this are so common from people using monorepos that I am convinced ...
Why is there no contact form?
Is something like this always just a hack/shortcut or are there people who want this as their ideal workflow?
Is something like this always just a hack/shortcut or are there people who want this as their ideal workflow? I'm curious because I see stuff like this all the time being submitted to YC. For example, is this for IT / DBAs that need to gather info for data analysts, marketers and sales people? Are there many people in that position and what would the ideal flow look like? I can see startups and small companies willing to use this as a stopgap, but I couldn't imagine larger customers/companies willing to use something like this. This isn't to say I don't know why this was built. The same forces are what drove us to build Wufoo. We were tired of building these tedious data collection apps. The DIY builder was out of laziness on our part. But when it comes to accessing existing data, there's so many concerns about security and privacy that I worry an idea like this will always be limited in terms of adoption. If people think differently, I would love to know.
Comments (0)
No comments yet. Start the discussion.