44 karma · joined November 25, 2017
I've been building with Python FastAPI and a React/Nextjs app. I've gone back and forth on whether we should have used Django, but we've been full steam ahead with what we have.
If I wasn't building in the AI space I think I probably would have used Node <-> React with tRPC to make the typed full stack monorepo experience seamless.
Oh and Postgres - I'm irrationally loyal to Postgres
Though I'm curious how they're not charging any subscription given that the device will have ongoing costs to run the models. That feels like it could hemorrhage money – though if users are actively using it I guess it'd be a good problem to have
I also think Cloud Computing has generally met the hype
With an updated LinkedIn you can reach out to past bosses, coworkers, and friends for introductions to other people in industry (whether they're hiring or not) – and follow that chain until you find something you're interested in.
An interesting example – I had a project where I needed to parse out addresses and dates in a document. However, the address and date formats were not standardized across documents. Utilizing LLMs was way easier then trying to regex or pattern match across the text.
But if you're trying to take a text document and break it down into some sort of a structured output, the outcome using LLMs will be much more variable.
You can add an OpenAI API Key and it'll use the GPT-4 API. It indexes your code for you and it'll crawl documentation for you if you give it the link. Then you can reference specific files or documentation with "@". There are also some really intuitive hot keys.
Really depends on the company I guess
> Is it sufficient to be skilled in one programming language, such as Python, and implementing a software renderer or ray tracer, your own neural network, your own HTTPS server, your own OS, your own memory allocator, your own interpreter, your own virtual machine...?
May be misunderstanding here, but if I was implementing my own OS I probably wouldn't be using Python. Different problems warrant different solutions – by a "general problem solver" I mean that you think about the coding language as a tool to solve a problem. Similar to how you might think of S3 or ECS as a tool.
That you're thinking of the problem in the business context rather than purely the technical context.
Not only on the OpenAI UI, but also via the Cursor IDE which I actively use with an OpenAI API Key.
Even if you don't use the OpenAI UI you'll likely end up using the produce via other products. Github Copilot, Arc Browser, Duolingo – likely more in the future – all use GPT under the hood.
The language, the stack, etc.. are just details. Given a problem - they can tackle it.
In a similar, but different vein, I've recently found interesting to think about how all the photos of yourself tend to live on other people's phones – whereas photos on your own tend to be of places and other people.
Honestly been pleasantly surprised now that they've had a subscription model for years and have honored my app purchase from probably over ten years ago
I've always liked the idea that if they didn't have a technical cofounder they might still be able to hack together an MVP using tools like Bubble, Zapier, Airbase, Sheets, etc.
Similarly, if you're doing something like generating medical/therapy notes, or generating SAT questions then GPT is great, but for transactions or cases where exact behavior is a requirement, then you sort of need a discrete set of instructions that only a programming language can provide. You're not going to see payments systems built by GPT in the short term at least.
And if the user did specify Hondas then why would Honda pay for it? Wouldn't the Chat bot give the same answer regardless of whether it's paid? I guess you pay for the CTA link?
Maybe a hot take, but I also think that over time coding makes you less casually/mindlessly social. Or maybe that's just getting older...