This is something that you can bootstrap into a proof-of-concept in a day and learn the tools you like and don't like along the way.
Basically you'll use any LLM and a vector DB of your choice (I like ChromaDB to date). Write a tool that will walk your source documents and chunk them. Submit the chunks to your LLM with a prompt that asks the LLM to come up with search retrieval questions for the chunk. Store the document and the questions in ChromaDB, cross-referencing the question to the document source (you can add the filename/path as metadata to the question) and the relevant chunk (by it's ID).
Run this tool whenever your docs change - you can automate this. Being intelligent about detecting new/changed content and how you chunk/generate questions can save you time and money and be a place to optimize.
To use it, you need to accept user input, run the input as a text query against your vector DB and submit both the results (with filenames and relevant chunks) and the user's query to a LLM with a prompt designed to elicit a certain kind of response based on input and the relevant chunks. Show the response to the user. Loop if you want.
You can build most of this with as few tools as `litellm`, `langchain` and `huggingface` libraries. You'll be surprised how far you can get with such a dumb setup.
Yes, this is basic RAG. That's how you do it without getting overwhelmed with all the tooling/libraries out there.
It isn't perfect and audio occasionally de-syncs or a speaker drops out. On a dedicated wireless channel playing a local source I imagine it would be pretty solid.
Not really an option if you don't have a Mac to run Airfoil, though if you do you can use the Satellite (https://rogueamoeba.com/airfoil/satellite/) program to sync Mac your other non-Apple devices to the host.
I moved out of Australia and let my bank know that I would likely be using credit cards overseas for a while.
Sure enough, as I was trying to buy furniture for my new place, the same thing happened to me. They blocked the card and when I called them they scolded me for not letting them know that I was traveling. I told the agent that I did in fact let them know, and asked them to update the account to note that I lived overseas.
Some 5 years later I needed to use one of those accounts again. I diligently phoned the bank, let them know I lived overseas and that I was going to use the card. I used the card, the transaction was blocked, I called and was again scolded for not telling them that I went on holiday.
I swear the 'notes' they add to your account are just an eye-roll and then a call disconnect.
I started building a Magic based data science tool for 6 months before coming to the same inevitable conclusion. It sits in a Github private repo rotting away.
That will depend on things you won't know until you start.
How much do you start with, what's your burn rate, how long until you get revenue, are you bootstrapping/funding, your personal cost of living, etc.
Running a business involves risk. Risk to your comfort, your mental health, physical health, financial health, etc. Closing a business is the end of all of that, not the start.
Why do you want to scratch that entrepreneurial itch?
> If I was thinking about driving through the Amazon I would ask others what the experience was like to better understand the risks, not just hop in the car and hope for the best.
Not what you are doing.
If you were probing to discover risks, you wouldn't be here asking what happens if your business fails. You would be asking how to prevent the business from failing.
> Are you saying that the best way to handle risks is to put your head in the sand and pretend they don't exist?
When it comes to entrepreneurship, yes.
You don't know what will come along and kill your business. Maybe Meta eats your lunch. Maybe the government in your jurisdiction passes a law that is incompatible with your primary monetization strategy. Maybe your house burns down and you need to sell.
Are any of these actually worth worrying over and planning mitigation against? Or are they your own personal black swan events that you just need to handle in the moment?
You know when the best time to worry about getting a job after your startup fails? When your startup fails.
To put it bluntly, this is all about mindset. You can't de-risk starting a company. You can only believe in your ability to overcome the obstacles that will come up as they come up. Planning what happens if you fail shows enough lack of belief in yourself that you almost de-facto will fail, because that exit door is always there if things get hard.
I have a devcontainer running the Cosmopolitan toolchain and stuck the cosmocc README.md in a file referenced from my AGENTS.md.
Claude does a decent job. You have to stay on top of it when it’s writing C, easy to turn to spaghetti.
Also the fat binary concept trips up agents - just have it read the actual cosmocc file itself to figure any issues out.