There is a heavy sentiment floating around lately. “Everything will be built automatically” “My craft is obsolete” “In six months, a tool will read my mind and produce whatever I imagine”I want to challenge this. Code is getting cheaper. Building is not.We are confusing capability with intelligence. LLMs are not AGI. They are not minds that can discover new physics on demand. They are...
and what about llm-scoring: does LLM output passed/not_passed or it is more?
Please share your current status :)
I'm curious about how people handle managing and iterating on their prompts, especially for production-facing prompts that many users depend on.- Where do you store your prompts? - Do you use version control? - How do you test prompts after editing? - Where do you store your test sets? - Do you evaluate results? If so, how? - Are you fine-tuning models like GPT-3.5 for better/cheaper results?
Is there a reason why new services are not using passwordless login? (Type your email -- receive the code -- fill in the code)
How do you decide which flow to implement: email-n-password vs facebook/google vs passwordless?
How did you search for it? Were you satisfied with the process and the results?
I'm wondering, are there more people like me who is sending links to themself to open those links on other devices or to keep it?
This is how a solution could look like: http://wrte.io
1) I think the fact of paying is already a good enough barrier. The price could be just a couple of dollars, which would be enough to convice sender to spend sometime on writing a personal email instead of using cold mail template.
2) Because of this barrier user will receive much less email + with much relevant content. As a result sender will have much higher chances for reply.
We think it will work for public people with tons of cold emails daily, like pg
Probably it is Gate's idea and many others :)
I've got very useful feedback from HN community previous time. Thanks a lot guys!
What was done:
- Changed the name (now it is searchable in the App Store by the name)
- Slowmo action to slow the game down for 15 sec
- In app purchase (slowmos)
- Pause button works now as it suppose to work
- Location achievements (Don't forget to allow location service)
- Bugfixes
In previous series: https://medium.com/@ivanpashenko/how-one-designer-was-learning-swift-cc2d99658895 https://news.ycombinator.com/item?id=8556056I've got very useful feedback from HN community previous time. Thanks a lot guys!What was done:- Changed the name (now it is searchable in the App Store by the name)- Slowmo action to slow the game down for 15 sec- In app purchase (slowmos)- Pause...