Dan Robinson Profile picture
Detail, prev Heap
Jan 26, 2023 6 tweets 2 min read
Want to build an AI infra company? Here's something I'd happily pay for.

Manage embeddings for me, *including the ability to refine off-the-shelf embeddings for my use case.*

Customized embeddings, as a service. Buried in the OpenAI cookbook is an absolute gem of a guide by @sandersted on how to do this.

Given pairs of items that should be close together in embedding space, you can train a simple map on top of the outputs of a baseline embedding model. github.com/openai/openai-…
Jan 8, 2023 5 tweets 1 min read
RETRO models are a giant capability unlock for LLM tech, and they're shockingly under the radar.

The first ones should come out this year. They might be even more significant than GPT-4. You can't "teach" current LLMs, the way you'd teach an employee. If they do something bad, there isn't a good way to say "don't do that."

You can include a reminder in every prompt, but that eats up precious context space.

You can fine-tune, but you need hundreds of examples.
Jan 3, 2023 8 tweets 3 min read
Introducing qqbot, a variant of ChatGPT that lives in your IDE.

The cool thing about qqbot is that it knows your codebase.

You can ask it questions like:
- Where is xyz implemented?
- Where are the tests for this function?
- If I want to implement xyz, where do I start? qqbot can help you navigate a large codebase.
May 16, 2022 28 tweets 5 min read
I stepped away from Heap last month, after nine fantastic years.

Here are some things I wish I could tell my 2013 self.

I was excited to write some code, and I had no idea what was in store on the path to 350+ people and a transformative product. 1/ What the company needs from a CTO is going to change every 18 months, often dramatically. You'll pretty much never get comfortable.

Being in a leadership role means your job isn't "technology". Your job is to make the company win. Get used to adapting around that.
Nov 8, 2021 15 tweets 4 min read
1/ What's a "technical moat"?

I get a lot of questions from SaaS founders about how to think about this.

Do technical moats apply to most SaaS products? What will stop a competitor from duplicating your product?

Here's the framework I use. 👇 2/ The point of a moat is to protect your differentiation. It's whatever would make it hard for a competitor to deliver the value you deliver.

Tech moats are interesting, because the tide of technology is always rising. It gets easier to build *anything* every year!