918 karma · joined October 15, 2016
The pricing for the smallest model is most enticing, but it's not available to me on my account for testing..
- as most work is inference, might not need for as many GPUs
- consumer cards (24G) could possibly run the big models
And specifically, seeing how going from 16fp to 8bit mostly gives same perplexity while anything further seems to lose quality / dumb down the model, how is this even less precise method is able to achieve this?
A man buys an apple, walks around, and sells it. Then, he buys two apples, walks around again, and sells them. Next, he doubles his effort by buying four apples, walking around, and selling them as well. Suddenly, he receives a phone call informing him that his wealthy cousin has passed away, leaving him a substantial inheritance. Now, the man is wealthy.
Granted it's not always easy and straight forward but that what senior developers in the team are for..
Strong typing really shines when you have generics, saving bugs at one level above basic types..
Use all the relational stuff but still have nice native support for JSON and useful extensions.
What else do I need?
Even now, with the addition of vector stores we get PGVector and so it just reinforces my choice over time.
While some things may be “easier”, all the marketing, sales and biz dev channels are saturated, “pay to play” as I see it, if you want to sell something.
Have a product? Great! Good luck getting visibility over all these zombie (live until money runs out) but funded startups.
I'm now adding "agent" functionality, specifically to enable the AI to do some "research" on the web, at the moment this will also be done without a framework.
So I'm either missing something or I am doing something simple enough that does not require the framework overhead / added value..
I am working to create this experience by augmenting the AI interaction with step-by-step leading questions and interaction UI, similar to how users would interact with a domain expert.
https://pth.ai Would love feedback! :)
If the latter is done based on a lie, then you cant align your “commercial purpose” and people who fulfill it..
I find user stories critical because they are the lowest common denominator for product/sales/dev/biz etc, everyone gets them, can agree if this functionality will or will not he in release X and pretty much would set expectation correctly between all parties.
Additionally, moving down the dev pipeline, once you have wireframes / more specific designs, you can go over the user stories to make sure they are all supported.