• 1 Post
  • 8 Comments
Joined 2 years ago
cake
Cake day: July 7th, 2023

help-circle
  • I have no advice but I’ve been thinking the same way. I like LLMs, I use LLMs, but the “shove an LLM into every product and call it more valuable” approach is not sustainable and it will fail. Hopefully not as a full on bubble collapsing economy thing, but it’s only a matter of time (I’d guess a year tops) until companies have to start admitting to losses and investors start retreating.

    Hopefully someone with some decent economic knowledge will drop some advice, but frankly I doubt anyone can do much better than guess (or parrot old advice) what will be least impacted. Intuitively tech stocks are the ones that will be hurt, maybe it’s manufacturing stuff that will stay more stable, but it’s all such a complicated web of interdependency who knows.


  • I just started using them and I like it. It’s a good balance of easy and secure for me. I just added the container to my stack and then use their UI to point a subdomain at the internal port. Security can go pretty extreme if you set up their whole zero trust thing.

    An alternative similar option is Pangolin. I’ve seen a lot of people like it to avoid Cloudflare, but I haven’t used it myself. There still has to be an endpoint running it, so you’ll need an external VPS, which then adds a cost to the equation but at least you control it.





  • I found this which is overkill for personal use but does a good job of laying out this sort of application: https://midday.ai/updates/automatic-reconciliation-engine/

    “Instead of just comparing text strings, we use 768-dimensional vector embeddings to capture the semantic meaning of transactions and receipts.

    // Generate embeddings for transaction data
    const transactionText = prepareTransactionText({
      name: transaction.name,
      counterpartyName: transaction.counterpartyName,
      merchantName: transaction.merchantName,
      description: transaction.description
    });
    
    const embedding = await generateEmbeddings([transactionText]);
    

    These embeddings allow our system to understand that “AMZN MKTP” and “Amazon Marketplace Purchase” refer to the same thing, even though the text strings are completely different. The system learns patterns like:

    • “SQ *COFFEE SHOP” → “Square Coffee Shop Receipt”
    • “PAYPAL *DIGITALOCEAN” → “DigitalOcean Invoice via PayPal”
    • “APL*APPLE.COM” → “Apple App Store Purchase””