vercel

Last few days have been a bit of a whirlwind. After creating and validating the proof of concept, it was time to sit down and think about an MVP. Assuming an MVP is a simple version of the product that (a) works, and (b) you’re allowed to charge for, this involves creating my own content database instead of stealing it (obviously). Running with the theme of building things as simply as possible, this in my current opinion means using my professional experience to whip up a Notion database (really, a collection of pages) of useful material, and then using Langchain’s Notion QA recipe to deploy something simple....

Day 88! Struggled yesterday and this morning to get my terrible MVP online. Actually, it’s not even an MVP. It’s really a proof of concept, if barely that. But Y Combinator says if it’s not shit, you waited too long to ship. So F it. Tried sticking it up on Vercel’s python runtime through a basic Flask app, but should’ve realized that the limits and timeouts relating to a serverless function architecture wouldn’t be the easiest way to get it up and running....