HN user

DelightOne

528 karma
Posts2
Comments431
View on HN

This time, I tried to learn from that: facts are stored as instants, reasoning happens in local days of the jurisdiction that cares.

I think that's how the JavaScript Temporal proposal works. Convert your instant to the timezone, make the comparisons/calculations, hope you didn't jump an hour due to summertime, convert back.

Making people able to sue for anyone feeling bad about not having gotten the job is a path you should not take. We have something similar in Germany and its horrible for companies. Leeches bleeding you dry.

Every time I hear it contains AI it sounds like the features' outcome will be uncertain. Especially with more experience. If your feature were good you wouldn't have to mention AI to show it is awesome.

More than not AI is used as an excuse for the feature to be bad.

The UX is not good enough yet. We would have to 1) show that it is reserved to people going on the link and 2) offer good/enough ways to be notified once the link becomes online and 3) need to know the likelihood of the link to actually work in the future based on prior commitment.

AND I probably forgot a couple of issues.

LLMs sure. My question is whether it is the same in practice for LLMs behind said API. I found no official documentation that we will get exactly the same result as far as I can tell.

And no one here touched how high a multiple the cost is, so I assume its pretty high.

We agree, solving binary search tree problems do not need solving. That's an old problem. Problem is if you need people to choose and adapt algorithms for a specific new problem, copilot will have a hard time and so you will have a hard time if you don't know how the algorithms work and never adapted one. Because copilots are not good at choosing the correct algorithm and adapting it for new problems, as far as my experience with the competitive programming course I took goes anyway.

If you have an old problem, copilot can solve it, true.