Flowmar. @flowmarhoops

@vitaliidodonov Stanley and I have already made plans for me to (FINALLY) start working on a project again that I have had on the back burner for a very long time. Thank you so much for reigniting the fire under me! @stanleyforx @vitaliidodonov and @pascalkordon

Win a share of 100,000 $SWEAT Prize Pool 🔥 🏆 50,000 $SWEAT x 1 of 300 Sweat Max Early Birds 🏆 5,000 $SWEAT x 10 - rules below To enter: ✅ Like & RT ✅ Tag 3 Friends Sweat Max is coming in January. Only 250 more Early Birds can get it today. Read more below 👇

Continuing the journey of optimal LLM-assisted coding experience. In particular, I find that instead of narrowing in on a perfect one thing my usage is increasingly diversifying across a few workflows that I "stitch up" the pros/cons of: Personally the bread & butter (~75%?) of my LLM assistance continues to be just (Cursor) tab complete. This is because I find that writing concrete chunks of code/comments myself and in the right part of the code is a high bandwidth way of communicating "task specification" to the LLM, i.e. it's primarily about task specification bits - it takes too many bits and too much latency to communicate what I want in text, and it's faster to just demonstrate it in the code and in the right place. Sometimes the tab complete model is annoying so I toggle it on/off a lot. Next layer up is highlighting a concrete chunk of code and asking for some kind of a modification. Next layer up is Claude Code / Codex / etc, running on the side of Cursor, which I go to for larger chunks of functionality that are also fairly easy to specify in a prompt. These are super helpful, but still mixed overall and slightly frustrating at times. I don't run in YOLO mode because they can go off-track and do dumb things you didn't want/need and I ESC fairly often. I also haven't learned to be productive using more than one instance in parallel - one already feels hard enough. I haven't figured out a good way to keep CLAUDE[.]md good or up to date. I often have to do a pass of "cleanups" for coding style, or matters of code taste. E.g. they are too defensive and often over-use try/catch statements, they often over-complicate abstractions, they overbloat code (e.g. a nested if-the-else constructs when a list comprehension or a one-liner if-then-else would work), or they duplicate code chunks instead of creating a nice helper function, things like that... they basically don't have a sense of taste. They are indispensable in cases where I inch into a more vibe-coding territory where I'm less familiar (e.g. writing some rust recently, or sql commands, or anything else I've done less of before). I also tried CC to teach me things alongside the code it was writing but that didn't work at all - it really wants to just write code a lot more than it wants to explain anything along the way. I tried to get CC to do hyperparameter tuning, which was highly amusing. They are also super helpful in all kinds of lower-stakes one-off custom visualization or utilities or debugging code that I would never write otherwise because it would have taken way too long. E.g. CC can hammer out 1,000 lines of one-off extensive visualization/code just to identify a specific bug, which gets all deleted right after we find it. It's the code post-scarcity era - you can just create and then delete thousands of lines of super custom, super ephemeral code now, it's ok, it's not this precious costly thing anymore. Final layer of defense is GPT5 Pro, which I go to for the hardest things. E.g. it has happened to me a few times now that I / Cursor / CC are all stuck on a bug for 10 minutes, but when I copy paste the whole thing to 5 Pro, it goes off for 10 minutes but then actually finds a really subtle bug. It is very strong. It can dig up all kinds of esoteric docs and papers and such. I've also used it for other meatier tasks, e.g. suggestions on how to clean up abstractions (mixed results, sometimes good ideas but not all), or an entire literature review around how people do this or that and it comes back with good relevant resources / pointers. Anyway, coding feels completely blown open with possibility across a number of "kinds" of coding and then a number of tools with their pros/cons. It's hard to avoid the feeling of anxiety around not being at the frontier of what is collectively possible, hence random sunday shower of thoughts and a good amount of curiosity about what others are finding.

x.com/i/article/2010…

Send this to every normal person you know because normal people don’t want to touch a terminal and this will make them 100x more powerful and productive at whatever is they do

Claude @claudeai

5 months ago

Introducing Cowork: Claude Code for the rest of your work. Cowork lets you complete non-technical tasks much like how developers use Claude Code.

3K 8K 86K 49.7M 58K

@easytoolshq SEND

@carlvellotti Claude

Everyone should learn Claude Code! So I made a FREE course for non-coders! 🎉 [⚠️ Comment "Claude" & I'll DM you the link] By now, you've probably heard: → Claude Code is not just for code. It's a powerful AI agent that can help you with basically anything you do on the computer. I really mean anything. Writing, research, design, building, emails, life stuff – Claude Code helps you do all these things better and faster than ever. I personally use Claude Code all day, every day. And I've never even been nearly as productive as I am now. This is the future. Over 2000 PMs have completed my Claude Code for PMs course. People keep saying – "it's aimed at PMs but useful for everyone." So I'm launching... 🥁🥁🥁 Claude Code for Everyone! 🔹 Complete guide for non-technical people 🔹 Analyze files, run research, build systems 🔹 Free! Other courses literally charge $1,000+ The most awesome part: → Learn Claude Code IN Claude Code! You'll work through realistic files directly IN Claude Code, so everything is applicable. It's really cool. People have literally called CC for PMs a masterpiece 💅 Even if you are completely non-technical, this guide helps you at every step of the way. Here's exactly what's in the course: Module 1: Claude Code Core Features 🚀 1.1: Introduction 🔍 1.2: File Exploration 📁 1.3: Working with Files ⌨️ 1.4: Commands 🤖 1.5: Agents 🎭 1.6: Sub-agents 🧠 1.7: Project Memory ⚡ 1.8: Power Features Intro And this is only the beginning: Coming Jan 15: Vibe Coding 101 → Actually build and deploy something! → Vibecode guides NEVER teach deployment → Zero coding background needed Coming next: → Connect AI to Everything (MCPs & APIs) → Complete Guide to Skills → Advanced Vibecoding Plus – this will become THE Claude Code community for sharing: → Definitive resources → Creative use cases → Proven prompts Claude Code has changed my life. I bet it will change yours. ⚠️ Do these things to get it: 1. REPOST this post 2. FOLLOW me so I can DM 3. COMMENT "Claude" & I'll DM you!

I just joined the waitlist for Jobloo - The Tinder for Jobs! 🚀 AI applies for you automatically. Check it out: jobloo.co

@sunglasssister This is quite the change in pace and attitude. Hmm...

@FKAtwigs I know I'm super late but oh my freakin AHHHHH "Drums of Death" takes my soul to a whole new level of unified dichotomy. All the love in the world to you. ❤️

@dhh Excited to try this out soon!

@sunglasssister someone help her little basic face and tell her that she's holding onto nothing Imma send some flowers to her ego so at least she walks away with something

@sunglasssister Why would they? Girl, chill tf out.

Of all days I decide to open up this app... It's today? Funny. #MyXAnniversary

Here we go... Time for my YouTube journey to begin. 🌈❤️🔥💙

@ThriveCart 200

@clipstudiopaint heyy

@DEATHPACT A. E. I. O. U. are vowels and...

I just published my latest article: “THANK YOU SO MUCH FOR THIS!!!” on @Medium ift.tt/93EvSuQ