I build & teach AI stuff. Building @TakeoffAI. Learn to build with AI at https://t.co/oJ8PNoAutE.
8 subscribers
Dec 20 • 7 tweets • 3 min read
We now live in a different world.
Acceleration is imminent.
You *will* need to adjust your worldview.
This is what the early days of the singularity look like.
And you are living through them.
There is absolute no situation in which you will outcompete someone who is using o3 and you are not.
This clearly seems like the model that will begin to actually spark a real AGI debate.
Based on the numbers they’re showing today?
Not sure I’d argue against it.
Dec 15 • 4 tweets • 2 min read
I asked o1 pro to implement 6 things I had on my todo list for a project today.
- It thought for 5m 25s.
- Modified 14 files.
- 64,852 input tokens.
- 14,740 output tokens.
Got it 100% correct - saved me 2 hours.
Absolute powerhouse.
Including my o1 workflow video + GitHub link to my xml parser for the ai code cowboys out there who want to come explore the wild west.
Here’s how to use OpenAI’s new o1 pro model to maximize coding productivity.
I’ve used this workflow for the last 48hrs and I estimate it has 2x’d my output.
Watch the full 19min tutorial.
Prompt below.
Actual workflow demo at start.
17:00ish for tool stack.
Here’s the full o1 XML prompt:
—
You are an expert software engineer.
You are tasked with following my instructions.
Use the included project instructions as a general guide.
You will respond with 2 sections: A summary section and an XLM section.
Here are some notes on how you should respond in the summary section:
- Provide a brief overall summary
- Provide a 1-sentence summary for each file changed and why.
- Provide a 1-sentence summary for each file deleted and why.
- Format this section as markdown.
Here are some notes on how you should respond in the XML section:
- Respond with the XML and nothing else
- Include all of the changed files
- Specify each file operation with CREATE, UPDATE, or DELETE
- If it is a CREATE or UPDATE include the full file code. Do not get lazy.
- Each file should include a brief change summary.
- Include the full file path
- I am going to copy/paste that entire XML section into a parser to automatically apply the changes you made, so put the XML block inside a markdown codeblock.
- Make sure to enclose the code with ![CDATA[__CODE HERE__]]
My #1 takeaway so far after using OpenAI’s new o1 model…
We’re about to have the ChatGPT moment for agentic coding systems.
o1’s ability to think, plan, and execute is off the charts.
The wave of products that will be built with this will be unlike anything we’ve ever seen.
Expect the Cursor Composers, Replit Agents, Devins, etc of the world to take a massive leap.
Will take a little bit of time bc standard prompting techniques aren’t that effective so we need to learn the system.
But expect many more tools like the above for various professions.
Aug 29 • 5 tweets • 5 min read
In Cursor I’m able to generate a fully functional backend with a single prompt.
A working database in <2min.
Composer is pure magic.
Full prompt below.
PUT THIS PROMPT IN A `` FILE:
--
# Backend Setup Instructions
Use this guide to setup the backend for this project.
It uses Supabase, Drizzle ORM, and Server Actions.
Write the complete code for every step. Do not get lazy. Write everything that is needed.
Your goal is to completely finish the backend setup.
## Helpful Links
If the user gets stuck, refer them to the following links:
export type InsertExample = typeof exampleTable.$inferInsert;
export type SelectExample = typeof exampleTable.$inferSelect;
```
- [ ] Export the example table in the `/schema/index.ts` file like so:
```ts
export * from "./example-schema";
```
- [ ] Create a new file called `example-queries.ts` in the `/queries` folder with the following code:
```ts
"use server";
import { eq } from "drizzle-orm";
import { db } from "../db";
import { InsertExample, SelectExample } from "../schema/example-schema";
import { exampleTable } from "./../schema/example-schema";
We’re at the point with AI codegen where Cursor + Claude 3.5 Sonnet is a legit technical cofounder.
The ceiling on complexity that it can handle will continue to go up over time, and this will happen quite quickly.
We are still early, and it’s already this good.
Learn how to communicate clearly and manage context effectively.
Do not let others tell you what you can’t build.
Aug 7 • 4 tweets • 1 min read
Here’s a 17min deep dive on advanced prompting techniques for LLMs.
Fully demonstrated on a real-world, multi-step AI workflow.
Watch for a complete breakdown.
The video covers:
- prompt chaining
- chain-of-thought with <scratchpad> tags
- xml tags
- system vs. user messages
- output parsing
- prefilling
- information hierarchy
- role prompting
- goal prompting
- recursive llm calls
Lots of good stuff in there!
Mar 13 • 5 tweets • 1 min read
I’m blown away by Devin.
Watch me use it for 27min.
It’s insane.
The era of AI agents has begun.
Devin feels like the ChatGPT moment for AI agents.
Exceptional work from the Cognition team.
It’s going to be fun to experiment and figure out where it’s most useful in its current state.
This is the worst it’ll ever be - the future is bright!
Jun 8, 2023 • 4 tweets • 2 min read
ChatGPT just killed Siri.
You can now:
- use ChatGPT with Siri
- start new chats
- continue old chats
- sync chats to ChatGPT app
I built “Let’s Chat” so everyone can take advantage of this and have a more powerful AI voice assistant!
AI is bringing in a *massive* new wave of people who are learning to code.
Why?
They want to run & build AI programs!
One of the interesting developments around this is that GitHub is becoming a sort of AI App Store.
And git clone is now the download button for AI apps.
I’ve seen a lot of pathetic gatekeepy behavior from programmer vets towards our new friends.
“Oh noooo auto-gpt has more stars than PyTorch now what are we gonna dooooo.”
How about encourage them?
More people are discovering the magical world of software - welcome them! :)
Apr 16, 2023 • 4 tweets • 1 min read
AI music is here.
This is the 1st example of AI generated music that *really* wowed me.
This guy ghostwriter977 on TikTok made a Drake x The Weeknd track that’s actually kind of insane?
You’ll soon be able to make unlimited music by your favorite artists on demand with AI.
If you told me this was a leak from an old mixtape I would’ve 100% believed you.
Imagine where this is in a year…
Obviously there are a ton of major copyright questions and whatnot, but you can’t deny that this is going to became a huge thing *really* quickly.
Apr 15, 2023 • 4 tweets • 2 min read
Introducing AI Brainstore!
It’s a proof-of-concept of a brain for an AI agent.
Ask an agent a question, it checks its memories for an answer, otherwise it browses the web and learns the answer.
My GPT-4 coding assistant can now build & deploy brand new web apps!
It initializes my project, builds my app, creates a GitHub repo, and deploys it to Vercel.
All from simply using my voice.
Built with @CodewandAI.
Our 1st tool (of many coming!) comes out soon.
It’s not this one, but this feature is on the way.
Excited to start sharing these next-gen AI devtools with you.
Mar 29, 2023 • 5 tweets • 1 min read
What if writing code was as simple as talking to your device?
Watch my GPT-4 voice assistant:
- take in a complex coding task
- write the code
- create a PR on my GitHub repo
All I had to do was tell it what to do.
This is the future of software.
Powered by @CodewandAI.
(and yes I can use it on my phone too but I need my phone to film haha)
Mar 29, 2023 • 4 tweets • 1 min read
The issues with Chatbot UI & OpenAI have been resolved.
Huge thanks to their team for the quick response and the clarity on what happened.
OpenAI was *exceptionally* helpful here, and it’s very important to me that you all know that.
Now… back to building!
And I apologize for taking down the site without warning.
Didn’t have any interest in legal issues so I complied immediately.
I’ll always do anything I can to keep it up for you if you can’t run locally!
I pay a decent amount out of pocket to keep it up bc I believe in it.
Mar 29, 2023 • 4 tweets • 1 min read
I have been informed that I need to take down the hosted version of Chatbot UI immediately.
If anyone at OpenAI could clarify the issue I would appreciate it.
Is it the name? Is it the UI?
I love OpenAI, and I just want to build a good open source UI with tools for users.
I’m really hoping it’s just a naming conflict that they want resolved, and if so I get it and am happy to change it.
I truly think the world of OpenAI - everyone there has been very kind and helpful to me and I admire them greatly as an organization.