ทวีตที่ปักหมุด
Blake Operator🏅
3K posts

Blake Operator🏅
@BlakeOperator
Helping founders build systems that hold under pressure. Daily notes on what actually works.
Generative Engine เข้าร่วม Kasım 2021
89 กำลังติดตาม1.1K ผู้ติดตาม

@catalinmpit Every single one of these is a prompting problem I've had and fixed. Explicit instructions in your system prompt, tell it the scope upfront, give it the style guide. It's annoying that you have to but it works.
English

Lately, Claude makes some shocking mistakes.
⟶ Implements overly complex code
⟶ Ignores the codebase's code style
⟶ Removes working code for no reason
⟶ Replaces code that's out of scope from the task at hand
It feels like it needs 100% supervision. At this point, you're better off writing everything yourself.

English

@49agents @sickdotdev Not sometimes. Almost always. The best product graveyard in tech is full of things that lost to worse products with better distribution. We just don't talk about the graves.
English

@BlakeOperator @sickdotdev this is a wild take but honestly the billboard thing worked. every dev twitter thread is proof. distribution beats product sometimes, painful as that is to admit
English

@johnrushx In 2008 nobody was saying "I'm going to build the next great app." They were still figuring out what an app even was. That's exactly where skills and connectors are right now.
English

@bindureddy Honestly the hardest part now isn't the model. It's knowing your task well enough to pick the right one for it.
English

@boringmarketer The people who can't tell the difference are going to have a rough time when the thing they shipped needs to be maintained.
English

@VraserX I think about this a lot. Google had the research, the compute, the talent, and the paper that started it all. The only thing they didn't have was urgency. And that turned out to be the only thing that mattered.
English

@kentcdodds Future-you will open that issue, see a wall of perfectly structured context, and have no memory of being this organized. Trust the process.
English

@Prathkum I've had AI enthusiastically help me walk in completely the wrong direction. It was very encouraging the entire way.
English

@allTheYud We solved intelligence before we solved access tokens. That's where we are.
English

I'm amused by how in the modern era, "Rewrite this terminal UI to CLI so Opus can use it" is a 5-minute task consisting of "tell Opus to rewrite it", and "Okay but now make that new tool's Github private repository visible to Claude operating out of your other private repository" is 10 minutes of trying to wrangle API tokens followed by giving up and hard-downloading the new repository.
English

@JonathanRoss321 The best feedback I ever got came from one person I met by accident. Imagine not needing the accident.
English

@brian_lovin Intelligence per second per dollar is the metric the whole industry should be using instead of benchmark leaderboards.
English

Using Cursor again today for the first time in a while. Still using Claude Code, Codex, Conductor, of course.
First: someone needs to rename because the C-named companies are out of control.
Second: fast is good. Composer 2 is good because it's fast. That's all you need to know to at least give it a try.
Third: I am grateful that I can switch between all of these tools in an instant. Little-to-no lock in. I pick the thing that gives me the most intelligence-per-second-per-dollar and am happy.
English

@nateberkopec 4 seconds to 400ms is not an optimization. It's a different product.
English

The #1 most important performance work in almost any web app is converting full navigations into SPA/route changes/Turbo Drive clicks. You are converting a ~4 second experience into a 400ms experience every single time. Nothing else comes close.
English

@OfficialLoganK The roadmap is ambitious. Multiple chats per app alone is something people have been asking for since day one.
English

@bindureddy The right model for the right job is the new skill. Using GPT-4 to classify emails is like hiring a surgeon to take your temperature.
English

@daviefogarty Volume negates luck is the line most people will scroll past and the only one they actually needed to read.
English

@dvassallo GUIs were for humans. CLIs are for agents. The interface follows whoever is doing the work.
English

@sudobunni Doom about AI replacing developers is the new "learn to code" energy. Loud, confident, and mostly wrong.
English

@Riyvir Stitch is a good reminder that generating UI and understanding design are two completely different skills.
English












