Using your machine "until I found out whether they were serious enough to properly supply the necessities." makes no sense whatsoever. They aren't. You don't need to waste any energy finding out, they fact that they asked gave you your answer.
21,688 karma · joined November 3, 2013
hikingdave @ gmail.com
Using your machine "until I found out whether they were serious enough to properly supply the necessities." makes no sense whatsoever. They aren't. You don't need to waste any energy finding out, they fact that they asked gave you your answer.
Run away.
No, and neither does anyone else in these scenarios. Almost all startups are trying to build something new that they want people to want. But customers almost universally do not want your product. They don't give a crap about you or your product. What they care about is delivering their own product and/or achieving their own goals. Your product is a tool. If it is a tool that helps them for a reasonable price, they will buy it. But never be fooled into thinking "They want my product". They don't. They want an effective tool to to meeting their own needs. Your product wins when it is that tool.
How do you all address such concerns, and handle throttling your data gathering in order to not become a problem for the original content providers?
Seems like they covered your points just fine. They just did it succinctly and trusted the reader to understand the broader implications.
I don't agree with their premises and they lost me early on when they posited that the only reason anyone ever coded locally was to avoid network lag. I'd argue price, simplicity, performance, mobility, isolation of your changes, and probably half a dozen other reason I'm forgetting are in that mix, too. I'm sure that in some ways I am an old grey-haired dude whose comfort zone is outdated, but at the same time, if you want to move beyond the old ways of doing things, and create something new, you need to understand why the old ways existed.
This post/advertisement doesn't indicate to me that they started with that baseline of understanding.
Yes. But have you considered that one of those consequences could be that companies who are not pushing AI will see that and give you an interview.
If you have criteria that would make you reject a job, regardless of how unpopular it might be, you should be shouting it form the rooftops. Any company who chooses not to engage with you because of it is saving you time and energy. Any application that gets no response because of it saves you from an interview process that would have failed, or worse - a job you would have hated. Which means that anyone who is engaging with you for interviews already knows your opinion and they are OK with it.
BTW, I'm not sure your opinion is unpopular. The concept of the "vocal minority" seems to be at play these days, as for every dev I know and work with who is positive about AI, 2 others are negative about it.
That is actually the key phrase. HN can provide the API, no problem. People can consume the API, no problem.. But I'd ask an attorney if API consumers can then re-release the data for purposes not related to YC. By my reading, they cannot.
You are making a huge pile of assumptions about who "we" are. This is a pile of statements you have learned about yourself. But you are missing the fact that everyone is different. If this formula and way of thinking works for you, great. Thanks for sharing it, maybe someone else will gain some insights as well.
But you are not speaking universal truths here, you are speaking personal lessons.
From the HN Guidelines: please use the original title, unless it is misleading or linkbait; don't editorialize.
If so, that is incorrect. They use the binary values. The actual difference between IPv4 and IPv6 is that IPv6 uses 128-bit addresses, not 32. So you can devise whatever human-readable abstraction you like, it won't change how networking actually operates.
And if you don't have specific user you want to look at, you can look at the top 100 users here: https://news.ycombinator.com/leaders
You can also find the recent "best comments" here: https://news.ycombinator.com/bestcomments
That is a hefty set of assumptions you are making there. There is no guarantee such a reality will ever exist, and decent odds against it.
At the same time, if you consider it to be a virus or malware when an LLM generates and runs code that harms a product or device... we are already there. Agentic AI with too much system access is already a thing. Just look at the anecdotes of "My AI deleted by database!" and other such stories.
My point being - your UX doesn't ask what people's goals are. Not everyone wants a "perfect lawn". Even people who do want grass may have different priorities for their grass - low maintenance vs. low water usage vs. really green, etc.
If you want your product to be different than what the lawn care guys will say, then you need to actually let people do different things in the app. Or, if you are dead set on making this into lead gen for lawn care guys, well... I personally find that somewhat disheartening, but clearly I'm not your audience.
If you are looking around and saying that because people aren't waving sign on street corners, then nobody cares, then you have utterly missed a couple decades of dedicated efforts by many people working around these issues.
The fact that shootings still happen is tragic. But it is not because people are just shrugging and saying they don't care.
Keep in mind that for all the troubles and trauma caused by the current USA government, they are really good at manipulating the legal system to get their way. This is just another example of it.
I know that sounds dismissive, but if you have so much billing going on that you are out-scaling Stripe's limits, surely you could afford to research other options?
QR codes are nothing more or less than a way to represent a chunk of data. They already are exactly what this site advertises. Sounds like they must have had a friend who got burned by a QR code that pointed to a URL where some content expired... but that doesn't have anything to do with the QR code itself.
Or were you only asking about digital tools? I haven't really made any of those. Making physical tools feels much more satisfying these days.