HNHacker News
TopNewBestAskShowJobs

willd13

4 karma · joined February 20, 2024

submissionscomments
willd13··on OpenAI Model Spec
Really interesting, this is an attempt to provide documentation for a piece of software with outputs that aren't deterministic.
willd13··on How about trailing commas in SQL?
Trailing commas are an abomination
willd13··on Show HN: An AI-powered book software to write a book in hours
This is cool tech, but also a slop machine.
willd13··on Ask HN: Human vs. Computer in Rock Paper Scizzors
When a computer plays poker, it bluffs. That is part of the optimal strategy.
willd13··on Kobold letters: HTML emails are a risk
Still pretty cool trick though
willd13··on Manipulating Chess-GPT's World Model
I would be really interested to understand the efficiency of this learning vs a more traditional approach. If you have two models - ChessGPT and a traditional chess-playing ML model - and train them on the same number of games, which reaches a higher level of chess-playing skill?
willd13··on Ask HN: What do data scientists need to know about LLMs to be competitive?
You say you have no experience with deep learning. Start by learning about "traditional" deep learning models, then move on to LLMs. Learning LLMs before deep learning is like learning algebra before addition.

"Deep Learning with Python, Second Edition" by Google's François Chollet is a pretty good intro, and also touches on LLMs / generative models towards the end.

willd13··on Ask HN: Some tips for evaluating intelligent agents?
What do you mean by an "intelligent actors platform"?
willd13··on Ask HN: How much to charge for an API call?
It depends on a lot of things:

a) Your business model Is the API your primary source of revenue? Something you'd be willing to lose money on in order to drive revenue somewhere else? You need to think about how it fits into the overall strategy of your business.

b) Your costs How much will this API cost you to setup, operate, and maintain? You need to think about how much you'll make/lose at different price structures and different volumes.

c) How the customer will use it Will they be looking to make 1 query a year? A million an hour? Probably somewhere inbetween of course, but that will make a big difference in terms of how to price it.

d) How much value does the customer get If using this API saves the customer $1 million in costs, you should make sure they are paying you at least $100k. If it saves them $10 in costs, make sure you aren't charging them more than $10. And again, you need to think about how much they are going to pay in total, thinking about how many calls they are making of the course of a day/month/year/etc.

... I'm sure I'm missing some. But the point really is, there is no right answer unless you think carefully about your product, customers, and strategy.