It seems like everyone is more worried about how something was made rather than what it is or whether or not the work is good on its own merit. Ironic from a group that is surely using AI tools in their own work.
If your application is pricing sensitive, check out DeepInfra.com - they have a variety of models in the pennies-per-mil range. Not quite as fast as Mercury, Groq or Samba Nova though.
(I have no affiliation with this company aside from being a happy customer the last few years)
Sounds great to me! Just be sure the AI is capable of taking on various personas because not everyone you meet is a believer in nonviolent communication.
A tip, Miami guy to Miami guy - the best devs eschew PHP like the plague. The remaining PHPers are desperate work-a-day sorts who will not be bringing the latest hotness to your project. Hire an Elixir or Haskell expert and you're gonna get a much more well-traveled coder.
Kudos on your bold undertaking! I've been a side-lined QNX admirer for some time, though not a potential user in most cases. A good next step would be a series of blog posts where the author takes on common types of enthusiast projects and unpacks how QNX's strengths can be applied in those scenarios.
Do you find you really need that level of “resolution” with memories?
On our [1] chatbots we use one long memories text field per chatbot <-> user relationship.
Each bot response cycle suggests a new memory to add as part of its prompt (along with the message etc)
Then we take that new memory and the existing memories text and feed it to a separate “memory archivist” LLM prompt cycle that’s tasked with adding this new memory and resummarizing the whole thing, yielding a replacement for the stored memories, with this new memory added.
Maybe overly simplistic but easy to manage and pretty inexpensive. The archiving part is async and fast. The LLM seems pretty good sussing out what’s important and what isn’t.
I have read a lot of reports that the job market is pretty bad.
But, bad or good, I think all you can really do is keep trying! Don't let a few rejections stymie your long term goals. Your family needs you to keep putting one foot in front of the other and applying to more and more places until you find that perfect role.
Maybe use this downtime to build yourself up: open source some stuff that defines you as a subject matter expert, or blog about some of your experiences, etc.
Wouldn't hurt to share your resume here too - lotta industry people lurking. :)
Sad day! This guy was a hilarious and talented writer. If anyone is looking for a book to pick up this weekend, I'd recommend checking out some of his work, especially if you like hard drinking Jewish nihilist detectives.
I still like that setup for using trees in low level languages.
But personally I’ve been working at higher levels of the stack the last few years, where these kinds of decisions seem less important.
And on another level, it seems like coders in general aren’t that interested in vector oriented languages and techniques which makes their study somewhat isolating.
Always surprising to click through a link on HN and discover it is one's own work. For a time I was very interested in lightweight array-based implementations of common data structures and this one seemed particularly handy.
I am experimenting with building software using the ReAct tool prompting pattern, using Llama derivative models like Manticore13B, Airoborous, etc. I script it all together using Microsoft Guidance with Llama.cpp and AutoGPTQ. Works pretty well for simple tasks and I know the costs are roughly fixed. Obviously their capabilities are far less than OpenAI's products but when you have tens of thousands of conversations to have the costs of ChatGPT become a distraction. Haven't tried finetuning yet.
cofounder of http://www.modernmethod.com/, makers of destructoid and other fine internet blogry
current projects:
GLORP, a search engine - https://glorp.co classic car price science - https://classic.com
tweeter @tlack email lackner at gmail dot com