Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

Bad lighting? Messy background? Wrong angle? 📸 Don’t delete that memory—ReShot it! ✅ Restore Clarity ✅ Declutter Scene ✅ Pro Remake Give your photos a second chance at perfection with Fotor AI. 👇 7 days only: Like + Repost + Comment = 50 FREE Credits! Web: App: #WaitDontDelete #ReShot...

38,711 görüntüleme • 5 ay önce •via X (Twitter)

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

Four AI agents increased the net-profit for an e-commerce business I work with by $47,000 in the last 90 days. I'm not talking about basic automations. I'm talking about AI systems that: → Generate professional product photos in seconds (no photographer needed) → Steal your competitor's best-performing Facebook ads and recreate them → Create unlimited influencer content without shipping a single product → Find qualified leads on Twitter 24/7 and convert them automatically All running while I sleep. No employees. No overhead. Just pure profit. The problem? Most e-commerce owners are still paying photographers $2-5K/month, burning ad budgets on creative that flops, and spending thousands per influencer post. I've been testing these agents for 4 months. The numbers are insane: ✅ $10K+ saved annually on product photography alone ✅ Ad creative costs slashed by 50% ✅ 47 influencer ads generated for $3 in API calls (vs $14K traditional cost) ✅ $3K in revenue from completely free Twitter traffic These four agents handle product photography, ad creative, influencer content, and lead generation - work that used to cost $6K+/month in freelancers and agencies. The e-commerce stores deploying AI agents like these are about to eat everyone's lunch while others are still manually creating content and bleeding cash on ads. Want the exact n8n templates for all four agents? Like & RT this post Follow me (so I can dm you) Comment "PROFIT" below I'll send you the complete systems for free, plus links to my YouTube tutorials showing the step-by-step builds.

David Roberts

19,909 görüntüleme • 10 ay önce

Eng Trans : 🦆🐰✅ Don’t forget to like, repost, comment on the original post. 👉 🦆🐰 Hellooo. 🦆 Today we’re going to check a list of things that if someone did them to Keng, whether #nampingster would be ok or not. (Note: 10 means the most not ok.) 🐰 Alright, let’s start. 🦆 Let’s start. 🐰 Harit, press it quickly. 🦆 Oh, the first one: squeezing cheeks. 🐰 Hmm… (thinking for a while) I think 8. Next. 🦆🐰 Holding hands. 🦆 Like a handshake, like this. (demonstrates a handshake with his own hand) 🐰 That seems normal. 🦆 Normal. 🐰 This one’s ok. (Namping gives it rank 3) Next. 🦆 Sitting on shoulders. (laughs) 🐰 Sitting on shoulders? 🦆 Maybe that would have to be a ghost. (laughs) (Note: In Thailand there’s a famous horror movie called Shutter where the main character is haunted by a ghost sitting on his shoulders. So when Thai people joke about shoulder riding or unexplained back pain, they often reference ghosts like in that movie.) 🐰 Hmm, sitting on shoulders might be difficult. Maybe once in a long while. 🐰 Actually I don’t think anyone would really do that. Ok, I’ll give it 4. Next. 🦆 Squeezing pimples. 🐰 (laughs) Maybe that would be a staff member or something. 🦆 Like when I go to a beauty clinic or something like that. 🐰 Ah, that one’s pretty chill. I’ll give it around 5, because they’re probably just doing their job. Next. 🐰 Wait… this one is kissing the cheek? (voice gets stricter, turns to look at #KengHarit ) 🦆 Maybe it could be a forehead kiss. 🐰 Hmm. (very cold tone) 🦆 Maybe the forehead. 🐰 That might be very not ok. I’ll give it 9. Next. 🦆 Tickling. (playfully tickles Namping’s waist) 🐰 Hey! (laughs) Tickling? (pauses to think) 🦆 Yeah, you’d have to be pretty close to tickle someone. 🐰 (thinks for a moment) Then 7. I might not be very ok with that. Next. 🐰 What is this one? 🦆 Slapping the face. That’s intense. (laughs) That’s a strong one. 🐰 (smiles) Slapping the face? Oh guys, don’t do that to P’Keng. We can talk things out nicely. 🦆 Or maybe it means touching the face. 🐰 Maybe it means touching the face. If it’s touching the face, that’s still not ok. I’ll give it 6 then. Next. 🦆🐰 Piggyback. 🦆 You’d have to be really close. 🐰 (looks very serious) That might not be ok. 🐰 If someone keeps doing that with different people, it’s not ok, because the other person might misunderstand and think too far. (Namping gives this a 10 in a serious face.) Next. 🦆 Oh, hugging. 🐰 Hugging is normal. (gives it rank 2) You can hug friends goodbye. Next. 🦆🐰 Bathing together! 🦆 (laughs and looks at Namping) 🐰 (stunned, eyes wide) And there’s only one number left, so it has to be 1. 🐰 But it’s a 1 that means not ok. 🦆 1 meaning not ok? 🐰 (nods) 🦆 But the not ok are supposed to be at the bottom. 🐰 That’s the only number 1 left. 🦆🐰 (laugh) 🐰 I’m satisfied with only 1 point and not satisfied with 9 points for this thing. (laughs) 🦆 Ok. (laughs) 🐰 Bye bye. 🦆 (waves goodbye) #KengNamping

DEAR U

31,485 görüntüleme • 5 ay önce

10 free Google AI tools nobody talks about. while everyone's burning $20/mo on chatgpt and claude, google quietly shipped a stack worth $200+/mo. all free. all yours. — 1️⃣ NotebookLM — your second brain upload sources (PDFs, websites, audio, YouTube). it summarizes, builds mind maps, generates quizzes, drafts slide decks, even turns your notes into a podcast you can listen to on a walk. free tier: 100 notebooks, 50 sources each, 50 chats/day, 3 audio overviews/day. replaces: notion AI + perplexity + readwise — 2️⃣ Google AI Studio — the free gemini playground web playground for gemini 3 pro and flash with a free API key. generous limits. paste a 1M-token context window and watch it actually use it. faster than the openai playground and free where openai charges per token. replaces: openai playground + paid API credits — 3️⃣ Gemini CLI — google's open-source terminal agent apache 2.0 licensed. one command (npx @google/gemini-cli) and you've got an agent in your terminal that reads your codebase, runs shell commands, and ships PRs. drop-in claude code alternative. replaces: claude code ($20/mo by default) — 4️⃣ Jules — async coding agent assign jules a github issue. it spins up a cloud VM, clones your repo, writes the plan, makes the changes, opens a PR. free tier: 15 tasks/day, 3 concurrent, runs on gemini flash. replaces: devin ($20/mo+) + cursor agent 5️⃣ Stitch — text → UI → code google's free figma killer. describe an interface, get production-ready HTML/CSS/Tailwind + figma export. march 2026 update added voice canvas, infinite canvas, and MCP integration with cursor. 350 standard + 200 experimental generations/month free. replaces: galileo AI + early-stage figma work — 6️⃣ Gemma 4 — open-weight LLM google's flagship open model. apache 2.0. 2B, 4B, 26B-MoE, and 31B variants. 256K context. runs on ollama with one command. quantized versions run on a 4090 or beefy laptop. replaces: paying for hosted LLM inference — 7️⃣ Illuminate — papers → podcasts paste an arxiv preprint link. illuminate turns dense research papers into a 6-8 min conversation between two AI hosts breaking it down. perfect for commute reading you can't do at a desk. note: still in waitlist for some regions. replaces: snipd + manual research reading — 8️⃣ Learn About (LearnLM) — adaptive AI tutor drop in any topic you're stuck on. highlight a word, click "go deeper," and the interface adapts in real time to your comprehension level. visual explanations, follow-up questions, the works. replaces: paid tutoring on niche topics — 9️⃣ Google Labs FX (ImageFX + Flow + MusicFX) — free imagen, veo, musicLM google labs creative suite. text-to-image (imagen 4), text-to-video (veo via Flow), text-to-music (musicLM). free tier: limited daily generations. the heavy veo 3.1 features are paid (AI Pro $19.99/mo). still worth using for image and music — those stay free. replaces: midjourney + suno (free tier only — runway-level video gen is paid) — 🔟 Google Colab — free GPU notebooks free T4 GPU + 12GB RAM in a browser tab. enough to fine-tune small models, run stable diffusion, prototype agents. the launching pad for half the ML projects on github. replaces: paid cloud GPU rentals — a quick honest note: these tools aren't 1:1 better than the paid versions they replace. but they're decent enough to get most things done — especially if you're not a heavy user or you've got little funds to play with. i've put all 10 in a public github repo (link in comments). follow + turn on post notifications for more useful posts like this 🔔

m0h

11,847 görüntüleme • 3 ay önce

Most guys do not realize how dirty, naughty, and sexual women are. The average woman is way dirtier than the average man. I don’t think I’ve ever met a woman who wasn’t turned on by public sex, for example. Very few men are as into it as women are. As a guy, when you’re about to get it on with a girl in public, she’s there moaning, telling you to “put it in”; meanwhile you are looking around to check if anyone else is nearby while positioning her in this uncomfortable public position in the dirt, in the cold, and telling her “all right, hold on, I’m working on it, let me just get it up here, give me a second, sheesh!” If you read a woman’s romance novel, there is so much ink spilled on teasing, build up, this sex act, that sex act, the other sex act, that it’s basically unreadable if you are a guy. As a guy, you just wanna get your hot dog in her hot dog bun. But women want to do all KINDS of stuff. There’s a million things sexually these girls want to do. So why aren’t girls jumping at the chance to go to bed with every guy they meet? ✅ She needs to TRUST a guy first. Trust that she is safe with him. Trust that he will not judge her. Trust that it won’t affect her reputation. Many men aren’t good at building trust. Trust is KEY. ✅ She needs some degree of attraction to the guy. Not NEARLY as much as most guys think. She does NOT need to be wild with desire for you to sleep with you. It is even possible to sleep with women who really are not attracted to you at all, but who are just bored (and horny) and you did the moves right. (Or, bonus round, you just offered her an experience she has always fantasized about, so even if you are not her dream guy, she nevertheless says fine, let’s do it.) ✅ She needs to be aroused. You know the whole “women’s arousal is like a dimmer” thing… it’s accurate. You need to ramp her arousal up with touch, teasing, flirtation, innuendo, sex talk, etc. ✅ She needs to be ALONE with you. If she trusts you enough, you can get her alone with you. Once she’s alone with you, if there is trust there, and there’s arousal, and maybe a bit of attraction, you will get her clothes off. Yes… even if she is a ‘good’ girl. ‘Good’ girls did not manage to pass down their genes by hating sex (they are just a bit more selective about the men they have it with, is all. They need more TRUST!). Also: don’t be UNNERVED by female sexuality. Every girl has a tigress inside her waiting for the right guy to unleash it… a guy who makes her trust him, arouses her, gets her alone with him, and maybe creates some attraction with her. Women’s romance novels are ALL about this. Women’s romances in real life are as well. In fact, in real life, women often settle for far less ideal situations: men they don’t completely trust, aren’t that attracted to, are only partway aroused by, who get them alone somewhere. The better a job you can do approaching her sexual “Platonic ideal”, the more reliably you can bring out that sexual tigress lurking inside of EVERY woman (even the ‘good’ girls).

Girls Chase 🏃‍♀️💨

34,136 görüntüleme • 8 ay önce

Proactive agent that thinks and acts like you. Multiplayer AI Brain for teams. Proper GUI for commanding 50 agents. all three. Sauna goes live today. First 2000 people, use access code LAUNCH for $80 of weekly(!) credits. Let’s explain. Multiplayer only works once the personal brain is powerful. So let's start here. Personal AI Brain 3,800+ tools connected. State of the Art memory. Skills and schedules you teach once that get repeated forever on cheaper models. An AI first CRM. Lives on the cloud so you can initiate tasks from anywhere: iMessage, Slack, Email. Also no need for a Mac mini 😉 GUI AI agents have been stuck in their MS-DOS era. A chat box, a scroll buffer, no way to command 50 of them. We built the first GUI: Live sessions on one side, work waiting for your sign-off on the other, plus the things Sauna kicked off while you were asleep waiting for review. Game mode helps clear the queue with actual joy. Okay so far so good, but how to give benefit of what you built to more people or whole team? Multiplayer Once your Sauna actually knows you and you gave her access to your tools, you can use multiplayer. Two modes: - Brain access. My co-founder Robert plugged my brain as a tool into his Sauna last month. He can ask it about pricing while I'm in other meetings, gets a sourced answer back, never has to interrupt me. That’s read only. Yolo mode gives him access to all my tools too :O - Communal Saunas extend that to whole companies with proper permissioning. Folder owners decide what's true for the whole company and build skills. Most get their personal brain + read access to communal files and memories. Works also for group planning my best friend's bachelor party. The Way I’ve been obsessed about AI Brain since 2016. Our human brains suck at some things like memory and are brilliant at others like creativity. We are also particularly bad at thinking we are all on the same page and then realising weeks later that we weren’t. Most leaders spend their days being the human diff tool, catching contradictions in hallway conversations and Slack threads. Repeating themselves 50 times. Now every company is spinning up hundreds or thousands of agents that drift faster than humans do, feeding each other their drift as context. Compounding rot. After 10 years and one failed company in this space we are launching the solution. The Launch We thought about a celebrity launch. Margot Robbie in a bathtub explaining agents. But then we realised the same money gives the first 2,000 people free daily credits, every day, until we burn through that $1,000,000. Sauna runs Claude, GPT-5, Gemini, GLM-5.1, DeepSeek, Kimi so you can budget yourself. The labs are racing to lock you so they can milk you in a year. We picked your side. Onboarding It’s live at We’ve preheated saunas based on a niche. Use the access codes in the comments to get a better experience.

Filip Kozera

783,569 görüntüleme • 3 ay önce

🚨 ATTENTION LONG ISLAND RESIDENTS🚨 Syosset Neighbors: Tomorrow’s Your Chance — Protect Your Community Values in One of America’s Most Jewish School Districts Attention Syosset families, Tomorrow, Tuesday, May 19th, 2026 is Election Day! Polls are open from 6 AM to 9 PM at Robbins Lane Elementary, H.B. Thompson Middle, and Syosset High School. This is your moment to decide who shapes your kids’ education in a district you have all worked so hard to keep excellent. Your community is one of the most Jewish on Long Island. Jewish families helped build this #2-ranked district through a shared commitment to academics, safety, fairness, and real integration and assimilation, not identity politics or imported conflicts from third world communities. But right now, three candidates for school board are standing out for all the wrong reasons. Brian Tvedt (#3), Lisa Li (#6), and Corey Witt (#5) are the only candidates who fully answered the Syosset Muslim Community’s 2026 Voter Guide. That guide pushes hard for: • Curriculum changes to spotlight “Islamic contributions” to society (I can’t think of any) • Heavy focus on “combating Islamophobia” (a made up term meant to protect jihadists from accountability) • More Muslim voices in school policies (this means the creation of anti-Jewish policies) • Expanded DEI and anti-bias programs that many parents see as one-sided and pro-Islam In a district still healing from post-October 7th antisemitism and threats of violence, this Islamic alignment raises serious red flags for Jewish families and everyone who wants neutral, balanced education free of Islamic indoctrination. Brian Tvedt has gone even further, speaking against the IHRA definition of antisemitism, calling Israel’s actions “genocide”, and tying himself to other controversial positions and Islamic causes. Every parent wants their kids to learn respect and get along. But that starts with neutrality in education, and not tilting the scales toward any one group’s agenda, especially when it risks double standards on bias, curriculum, or creating a hostile, pro-Islam school climate where Muslims are emboldened to attack Jewish students like they do in Mamdani’s NYC. Tomorrow, Take Action: ✅ Vote AGAINST Brian Tvedt (#3), Lisa Li (#6), and Corey Witt (#5) ✅ Support candidates who put academics, safety, and fairness first for every child: Jewish, Christian, Asian, Indian, and who oppose Islamic Jew hatred. ✅ Talk to your neighbors, friends, and family tonight. ✅ Get to the polls early. Bring your ID if needed. Every single vote counts in a local election like this. RECEIPTS 👇🏻

Laura Loomer

103,586 görüntüleme • 3 ay önce

Dear Friend, I wrote this book for you. For the past year, I have labored to create a product that will help you learn and master SQL. I have been there. I have felt the frustration of trying to learn SQL and not knowing where to begin. I have lived through the struggle of setting up a platform to run SQL queries. Most platforms require sign-ups and logins that create a headache for learners. I also know the challenge of finding proper SQL exercises that mirror the real-world experience of a data analyst. Yes, I have been in your shoes. That’s why I created SQL Essentials for Data Analysis: A 50-Day Hands-on Challenge Book (Go From Beginner to Pro). Yes, to give you a clear, practical path from beginner to confident SQL user. ✅Why SQL Still Matters You may be wondering if SQL still matters in 2025. The answer: it has never mattered more. SQL is the lingua franca of data. Data still lives in databases, and the only language it truly understands is SQL. Think about it, even in Python, SQL is there. You’ve probably heard about the powerful pandas library. Guess what? It also has some SQL. And don’t get me started on BigQuery, Tableau, Power BI, and Databricks; the answer is the same: they all rely on SQL. SQL is the big shadow that hovers over everything data. This is why learning SQL is a must for data analysts, engineers, scientists, and anyone working with data. SQL connects everything: exploration, extraction, transformation, modeling, validation, and reporting. ✅Why I Wrote This Book Dear friend, I wanted to create a resource that gives you everything you need to learn SQL for data analysis. Quite often, resources are scattered across different places. You might learn theory in one place, search for datasets in another, and hunt for questions somewhere else. More often than not, the only place you can tackle SQL challenges is online. But online platforms usually focus on syntax and don’t reflect the messiness of real-world data. I wrote this book to give you the best of both worlds: theory and practice. I don’t want you to be worrying about where to find resources. I want you to focus only on learning SQL. If you are new to SQL or need a refresher on the fundamentals, Part 1 of the book has you covered. If you are looking for practice, Part 2 is 49 days of hands-on SQL challenges designed to mirror real-world tasks. Each day in the book is designed to feel like a mini project, rather than isolated exercises. Take Day 15: Standardize Climbers Data, for example: On this day, you’re not just writing a single query; you’re working with a dataset from start to finish. By combining these tasks, you experience a full data preprocessing workflow, just like a real project. You get to practice loading, transforming, cleaning, and validating data, all in one challenge. This approach makes every day a hands-on project, not just an isolated query. You’re learning how SQL is used in real-world scenarios, not just memorizing syntax. By the end of each day, you’ve solved a problem that feels meaningful and practical: yes, something that mirrors data analysts’ and engineers’ work in real life. In this book I use SQLite. I chose SQLite because it’s simple, lightweight, and runs on any system without complicated setups or cloud accounts. You don’t need to worry about complex configurations. SQLite allows you to focus entirely on learning SQL concepts, queries, and logic without distractions. You will just have to import it. I also structured the book for use in Jupyter or Google Colab notebooks. These are playgrounds for data analysts, engineers, and scientists. These environments are interactive and flexible. They let you run queries, visualize results, and experiment in real time. Using notebooks ensures that you can practice SQL while documenting your work and learning at your own pace, all in one place. No need for sign-ups. ✅Why 50 Days? I chose 50 days intentionally. Learning SQL isn’t a sprint; it’s a habit. You can’t truly master a language by cramming a few queries in one sitting. 50 days creates a commitment. You attach yourself to a goal, a tangible outcome. Every day is a small win, a step forward, and by the end of the journey, you’ve transformed your understanding of SQL. By spreading the learning over 50 days, you build momentum, consistency, and confidence. Think of it like training for a marathon. You don’t run 26 miles on the first day. You run a little each day, gradually building strength, endurance, and skill. By the end of the 50 days, you’ll have tackled a wide range of SQL tasks: from simple filtering to window functions, date operations, joins, and performance tuning. You’ll have not just learned SQL but truly internalized it. The goal isn’t to overwhelm you. It’s to give you a structured, achievable path that fits into your daily routine, so learning SQL becomes natural, steady, and rewarding. Even if you don’t finish within 50 days, the 50-day structure gives you a rhythm, a habit, and a sense of accomplishment. The kind of outcome that sticks long after the book is finished. In summary, I wrote the book to address these pain points: 🔶Not knowing where to start: The book gives you a clear roadmap that guides you day by day. 🔶Too much theory, not enough practice: Reading about SQL is not the same as doing SQL. This book includes hands-on challenges that mirror real-world scenarios, so you’re not just memorizing commands; you’re learning to think like a data analyst. 🔶Complex setup: Many learners get stuck setting up databases or configuring environments. You will not worry about complex setups; everything runs in SQLite3 inside Jupyter Notebook, so you start immediately. 🔶Disconnected learning: The challenges mirror real-world analytics problems. Every day here is like a mini project, giving you the experience of exploring, cleaning, transforming, and analyzing data ✅What I ask of You I wrote this book for you because I want you to succeed, but books alone don’t create mastery; your effort does. I have provided the tools. All I ask is that you show up every day. Even if it’s just 20–30 minutes, take the challenge seriously. Tackle the problems, experiment with your queries, make mistakes, and fix them. That’s how real learning happens. I also ask that you trust the process. The book is designed to guide you from beginner to confident SQL user, step by step. Some days will feel "easy" and others "hard." Stay the course, and by the end, you’ll see how all the pieces fit together. Finally, I ask that you bring curiosity and persistence. SQL is a language of logic and structure, but it’s also a language of insight. The more you explore, the more patterns you’ll discover, and the more confident you’ll become in solving real-world problems. Don’t be scared to experiment. If you commit to this, I promise you’ll finish 50 days with more than just knowledge. You’ll have the skills, confidence, and habit of thinking like a data analyst. To make starting even easier, as a subscriber to this newsletter, I’m giving you an exclusive 35% launch discount. You can grab your copy today and start the 50-day journey at a reduced price. Grab SQL Essentials for Data Analysis here: I can’t wait to hear about your progress, the insights you uncover, and the confidence you gain along the way. If you have any questions, feel free to reach out to me or post them in the comments section. Let’s start this journey together: one challenge, one query, one day at a time. Warmly, Benjamin PS. Please repost.

Benjamin Bennett Alexander

16,883 görüntüleme • 9 ay önce

Important announcement!!!🫵💥💫 Would you have a tooth pulled if it helped your chances to get an important grant funded? Absurd question (obviously), but the situation right now is so bad funding-wise, that I bet some of you actually considered it for a second… Well, don’t get desperate - we created a new tool that might help! (keep your teeth!) I’m excited to announce that as of today we are officially releasing “QED for Grants” for everyone. What started off as an extension of our existing paper review platform, grew in the last few months to an entirely new design. We’ve been working like crazy on this, and although we have more things we want to add in the (very near) future, we decided to release our AI for grants NOW, earlier than planned. It’s not perfect, no AI is, but for the first time, when I run my own grants through QED Science, I feel it gets the research, finds real problems, and gives me very useful feedback that I can implement before submission. It’s like sending it to 20 scientists from my domain, knowing they’ll agree to dedicate their entire week to carefully read and comment on every line. It’s very important to write your own grants yourself, it makes you think hard and you learn a lot from doing it, and q.e.d’s system is designed to preserve these positive aspects and augment them - you get feedback on your own writing, we don’t write for you!! But at the same time, a typical PI spends many months every year writing proposals and sadly only a tiny fraction gets funded, even if the ideas are good. When you are forced to submit an unreasonable amount of grants the quality of the writing drops, and rejection rates increase. Not because the essence is bad. It’s simply too competitive right now (the cuts made it so much worse) and if your proposal is not super clear and tight, and if it’s not a perfect fit for the grant you’re submitting, you’re doomed. Our grant solution is not an authoring, text-generating tool. It gives you constructive feedback on your writing (it comments on the deep things, not grammar and typos). It’s meant to help you with the questions that torment you late at night (“is this a good fit?”, “Is this novel enough?”, “Did I miss something?”). Tens of thousands of you already use q.e.d to improve your manuscripts and critically read papers, we built the grant tool by the same principles (you’ll identify many of the features that you told us you like). We’ve processed thousands of proposals, learned where things fail, where reviewers get stuck, why good ideas come out weak. We interviewed hundreds of scientists, and also experts who work in funding agencies and university research authorities, and implemented their feedback (we’re constantly looking for more feedback). Our AI is always happy to give you constructive (and polite!) critique, and it will go through your grant line-by-line, forcing you to improve clarity, flag weak points, and push the whole thing to a higher standard. We study, in scale, what gets funded and what doesn’t, and what is the perfect fit for each type of grant. So please, use it, pressure-test it, tell us where it fails, and together we’ll improve it every day to put you in the best position for actually testing your ideas in the real world. As always with q.e.d, the system is completely secured and private, and we are NOT training on your data (see the FAQ on our website). Please like, retweet, and share with your favorite colleagues! (link to the platform below in the thread👇)

Oded Rechavi

49,579 görüntüleme • 3 ay önce

🎉 new skill unlocked: 20s uninterrupted, unstitched, single render from our new ai video engine: Nami. This is my birb (#7531) from the Moonbirds collection, idling in the library. patent: "Intra-Latent Semantic Injection via Cross-Spatial Encoding and Decoding during Multi-Pass Inference for Generative AI Video Creation" At Scrypted we've been quietly working on an agentic generative AI stack for two years: • integrating and testing w/ partners across the games & entertainment sectors • stealthily building a community of early believers through AVB • showcasing some of what we're doing with amazing projects like H011yw00d Agent. -- about Nami -- Nami is an agentic orchestration layer for AI video models: it unlocks their inner superpowers without making them rely on custom LoRAs or fine-tunings. Instead of throwing raw training power and tens of millions of dollars at training yet another ai video model: we figured out new ways to use what we have. Nami harnesses a multi-agent system to perform the work needed in taking a simple prompt or image and turning it into something bigger - much bigger. The agentic steps are allowed to manipulate latent space, digging into tensors, yet doing so in semantically aware chunks - meaning that Nami inherently supports video generation of arbitrary length, though it's bound to O(n) rendering time. (We do have some cool sharding tech that allows us to cut the generative time in half for a reference pose idle-animation like this demo). It's also fairly agnostic, picking and choosing the right tools for the job, and plays really well with emerging tech like FLUX Kontext, FramePack, or <- without being limited by any of them. -- use cases -- Even just a year or two ago the 20 second render below would cost a company, paying an agency, around $10k start-to-finish. This one cost me $6.25 on our dev hardware in an unoptimized environment. There's something mind-blowing about the state-of-the-art when we reduce costs to 0.0625% - less than 1% - of what we used to pay. It's also empowering. For creators. Game developers. Content influencers: you name it. -- superpowers -- 1. it does the things you ask for, in the order you asked for it 2. consistency is king 3. single-shot text or image-to-video 4. future videos can reference previous ones to seamlessly maintain style 5. semantic stitching: can't wait to showcase this -- gtm -- We think Generative AI Video, like image generation, like text, like games, should be a publicly accessible common good. We believe democratizing access to Nami in web3, via x402 payments proposed by Drew Coffman, or in World's mini-apps, is a bold step forward for digital freedom. Permissionless, decentralized, generative ai video. Naturally, we'll also soon release a web platform for using Nami in a traditionally SaaSy way: bring your own images, videos, or prompts and we'll take care of the rest. In the mid-term, Scrypted is building a stack of agentic skills (we call it AVB) and making them available to projects like H011yw00d Agent on Virtuals Protocol and other platforms. -- long-term vision -- Scrypted's mission is to decentralize the things that can't be decentralized. We participated in a16z crypto's CSX (London 2024) during our pre-seed specifically to research a new consensus protocol for hard things like AI video and AI agents: where there's no "one right answer". When Zero-Knowledge Proofs (ZKP) can't secure it, and Trusted Execution Environments (TEEs) are too small, we've got you covered with our upcoming Inori Network. -- how you can help -- 1. Are you a GPU farm? We're gonna need more flops. 2. Do you represent an L1 or L2? We want to build bridges. 3. Do you represent a Wallet or App creator? Let's get an endpoint exposed. 4. Are you an investor? Let's chat. 5. Like, repost, share! -- team background -- We come from a background of AI in the Video Game industry with each founder having over 20 years of experience at companies like Electronic Arts & Square Enix. -- contact -- DMs are open, reach out if you want to be an early tester for your site, game, collection, or project! -- try it out -- Go anywhere on X and tag H011yw00d Agent with a prompt and she'll give you a free 2 second render. Have fun making cinematic shorts or meme videos! -- thanks -- AWS Startups has been an incredible help scaling our prototypes. Also, shout out to all loyal beans 🫘 in the Autonomous Virtuals Beings (AVB) community. Nami has a very important role in the upcoming XP agent platform, can't wait to show you all. AVbeings

Tim Cotten

12,708 görüntüleme • 1 yıl önce

I MADE THE BEST 2D SPRITE AI PIPELINE EVER! After testing so much, doing tons of math, trying various different methods I finally got truly the cleanest sprite result I could ask for! You should bookmark this post! ✅ I think this is the happiest 'aha' moment I've had since starting this journey. Day 48 of making a custom webGL game engine using Cursor 🔽🔽🔽 I've been trying to solve sprites since I started this project. I came close a couple of times but it was always something - either dynamic lights wouldn't work, or the genAI results would make them grainy, or I would have to have incorrect alpha etc. After so much struggling, wanting to give up, thinking it's impossible - it was finally done! Perfect matte interpolation of black & white backgrounds resulting in a clean outline of the sprite, half transparent effects keeping their full quality. But this was not enough for me. I wanted more. I wanted those dynamic lights for the most badass anime effects that I'll be creating for the next many weeks! And somehow, I managed to come up with the perfect balance that is nice to the eye with almost no visible imperfections or artifacts when using any kind of dynamic lights. See for yourself! 🔽🔽🔽 How does this magic happen? 1⃣ First, the animation is created using Kling AI. I found it the best to keep the quality anime 2D style I wanted, but I guess others may work as well. 2⃣ Then, the frames are carefully extracted at lossless quality and processed via automation through Nano Banana pass to create an opposite background (white->black or black->white). 3⃣ Once we have a proper spritesheet, I then used MiDaS to compute the depth maps, and then algorithmically create PBR maps for lighting. The remaining depth maps can also be used for various effects, although haven't explored it much yet. 4⃣ Finally, all elements are cut into single frames and overlapped with their respective normal maps. If done right, they're pretty much ready for runtime. I like my heroes to be 512 to truly stand out like fighting game characters, but all of this works with far smaller or bigger sprites. Mind you, it's important to note that Nano Banana has a max output of 4k. Therefore you don't want to make your atlases larger than 4k - which is still quite a lot since it allows you 8x8 512 frames. 💡💡💡 I believe the output quality is beyond anything currently available, and I'll be looking into packaging the whole thing into a web app so people can use it. If you find this useful, please repost it! I really wanted to share this method to the world. Thank you for reading! Look forward to day 49 update!

Startracker 🔺

145,925 görüntüleme • 6 ay önce

How to Build a Proper Product Page It breaks my heart every time I see someone from Brazil, making just $200 a month, spend $40 on a test ad only to get a $2 CPC. Then, they cut the ad at $35 spend with 17 clicks and 0 conversions. What’s even more frustrating is when I visit their site and see it’s a complete mess. It’s like they didn’t even try. That’s why I’m making this post. *Disclaimer: If you're building a brand, this isn’t for you. This is for testing products correctly with a website that’s good enough to convert, but if you’re serious about your brand, hire a Figma designer and a developer to get things done right. As a fun fact, I tested the following product myself (In the video below) and with just one click at a $3 CPC, I got a sale with an $80 AOV (100% CVR). I paused the ads because the CPMs hit $150. If you're interested, save this product for the future. I'll share the creatives i used to ran the product with those who comment below. "jordan, stop teaching high school kids about selling reps and getting them sued by Prada or other big brands, ruining their payment gateways, and crushing their dreams." (with 5 random people only will do it, wouldn't make sense for everyone to be ripping it). Shoutout to Adrian for this one. 🫡 Back to the important stuff: Let’s talk about creating a great product page. First off, ditch the “Buy Now” button. By using this, you miss out on the chance to increase your Average Order Value (AOV) through upsells during checkout. Instead, replace it with an “Add to Cart” button. Also, remove the quantity selector. Hardly anyone uses them on the product page, but they do in the cart. Instead, offer bundles, which you can set up using the Kaching Bundles app or your theme if it supports this feature. The cart experience is crucial, and you can optimize it using the UpCart app. Enable all its product page features so it takes over the standard Shopify cart or your theme’s cart. The built-in cart systems are outdated—they don’t allow upsells like UpCart does. Plus, UpCart directly opens the cart after a product is added, where the upsell option appears at the bottom, increasing your chances of boosting AOV. Pay attention to color schemes. Don’t use neutral colors for headers and buttons if your product features a primary color. A yellow jacket with a black header is like pizza with raspberry syrup—just doesn’t work. If your product images are gray, white, or black, match those with your headers and buttons. Otherwise, play around with colors to give your page some dynamic appeal. Bookmark this site to get color palettes that match your primary color. For exact color matches, download the "ColorZilla" extension, which gives you the exact color code of whatever is under your mouse on the screen. If your product color is #6E402A, you’ll know it and can match it perfectly with your header and buttons, creating a visually appealing contrast like Cider did here below. Right now, when some of you send me these websites, they look like government pages from the early 2000s. Next, consider the typography and button styles. For fonts, use Helvetica Regular for body text and Helvetica Bold for titles, both at a minimum size of 100%. It’s simple and effective. As for buttons, they should have a corner radius of 8px. To change these settings, go to the theme settings - typography/buttons and adjust the buttons and typography accordingly. Rounded buttons create a modern, inviting feel, while full square buttons can give off an outdated vibe. Even casinos in Vegas design their buildings with curves, ensuring that visitors always have a view angle that draws them back in—it’s all about keeping things appealing and engaging. Finally, the product page layout itself should be clean and concise. Use collapsible rows for your product descriptions. No one wants to read a novel, so keep it compact and focused. Images and videos are what sell—this is why we don’t use text-heavy images in our ads; they just bore people. Keep the description short, with enough information to inform but not overwhelm. If you need to include more features, put them in the FAQs section—that’s what they’re for. The goal is to make sure that the "Add to Cart" button is visible as soon as possible once the customer lands on the product page, without overwhelming them but providing just enough information—some key benefits, high-quality images, and buying options in the bundles. Once they hit the cart, the upsells will do their job. Remember, the three essential apps for setting this up are Loox Reviews for customer feedback (use the product widget reviews at the bottom of the page before the FAQs and the rating widget just above the title), Kaching Bundles for offering package deals, and UpCart for optimizing the cart experience. Just for the record, this is to help newcomers and guide them to something taht works, me personally i don't use free themes, but this one i created could convert easily if the product, offer and ads match well. Good luck and keep testing! 🗳🥂💸🤑

Zzzz

42,318 görüntüleme • 2 yıl önce

Just in $AMD Anush "Speed is the moat"|ROCm🎙️ In the race to define the future of AI, what's the one advantage that truly lasts? It's not proprietary tech, argues Anush Elangovan Elangovan, VP of AI Software at AMD , but the sustainable speed of innovation. He explains why AMD is rejecting the "walled garden" model for its open source ROCm stack, betting that an open community flywheel is the key to victory. Listen to understand how this open strategy is designed to out-innovate closed systems by empowering developers to solve everything from frontier-model challenges to the mundane, everyday problems that define the "last mile" of AI. AMD ROCm Software: Part 1 Transcript [00:00:00] Andrew Zigler: Joining me is Anush Elangovan, VP of AI software at AMD. And when people talk about AI compute, the conversation often stops at hardware specs, but it's more than just physical chips that win the game. It's also the software ecosystems supporting them. [00:00:18] Andrew Zigler: The prevailing strategy in the industry has been to build something like a walled garden. You know, something closed, proprietary locks, developers in. But AMD is betting on an entirely different play, open source acceleration, and with rock, their open source AI software stack. AMD is building not just hardware parity, but an innovation flywheel that's powered by the community with interoperability and the freedom to scale without all of that pesky lockin. [00:00:48] Andrew Zigler: And in this world, speed is your moat and how fast you can innovate while your platform remains open, flexible, and standardize across all of its applications. That's what we're gonna explore [00:01:00] today. So Anush, I'm really excited to have you here. Welcome to Dev Interrupted. [00:01:04] Anush Elangovan: Thanks for having me. Uh, super excited to chat about it. [00:01:07] Andrew Zigler: Amazing. Well, let's go ahead and dive right in with kind of what I laid it out with in the beginning, the idea of the moat and it being about speed. I wanna unpack that a bit because that came from you when you and I first spoke. And I, and I want to know, you know, how do you define speed inside of AMD beyond just things like hardware, benchmarks. [00:01:27] Anush Elangovan: Yeah, that's a very good question. So when we typically talk about speed, everyone's like, Hey, hardware benchmark specs, right? Like, uh, memory bandwidth or, or flops. And that is one important part of it, uh, AMD does very well. With that, we do have, a, a very good history of executing on that axis. [00:01:47] Anush Elangovan: But when I say speed is the moat, it is about, uh, how we prepare, how we build the muscle to run the race for a long time and run it fast. And it is [00:02:00] not about a single point in time that you've, you've beat some you know, benchmark and, and you declare victory. It's about building the ability to consistently develop and deliver. [00:02:13] Anush Elangovan: Both hardware and software innovation at scale and do it fast, right? Like, you know, we we're increasingly getting to a point where models come out and they're, uh, you know, a year or two ago it was like, Hey, they work on AMD on day zero, which is great, but now they are performing on AMD the day it releases, right? [00:02:32] Anush Elangovan: So, what does it take to Prefetch where the industry is going? Be prepared to intercept. At that point is what you know, I, I refer to as you know, the, the speed factor in, in creating this mode, right? And the mode is just shed all things that hold you back and run as fast as you can. [00:02:53] Anush Elangovan: Uh, because the pace of innovation that is, uh, being seen in, in AI [00:03:00] industries is just. Amazing. Right? And it's like, it's transformational at at how you generate electricity. It's transformational as at how you build data centers. It's transformational at how you deploy compute, networking. It's transformational at what kind of use cases you, you know, uh, use AI for. [00:03:17] Anush Elangovan: Uh, and for that, you need to be prepared to, see what comes tomorrow and be prepared to run the race tomorrow. [00:03:23] Andrew Zigler: Yeah, it's a really great perspective because it highlights that it's not just like a checkpoint that you run through. I like how you called out, like it's not just hitting that benchmark or being the best in class at that moment, in that snapshot, it's about having a. The throughput and about having that dedication to the idea and continuing to deliver on it. [00:03:43] Andrew Zigler: It's not just crossing the threshold, but it's also being the engine. And that's what, that's what protects a business. That is the moat, because the moat is that innovation layer, the faster and more, uh, future forward. That you can work and think, [00:04:00] you know, the better. Uh, we, we talk a lot about like future forward work styles. [00:04:04] Andrew Zigler: Like what are the things I could be doing right now today that are gonna be like, way more useful tomorrow? Let, let's abandon those, workflows that are older and that kind of like, that translates into. An advantage when you work that way. You know, what kind of things have you learned working with, uh, like across all spectrums of people who would use ROCm, right? [00:04:23] Andrew Zigler: You have like the developers, but then you also have the enterprises and you have this large span of adoptees, right? So what is the, what does that look like that you learn? [00:04:32] Anush Elangovan: Yeah, so, so the way I look at it is there are gonna be pockets of different, uh, you know, cadences, right? Like, so people who are deploying in enterprises, for example, right? The validation and how long it takes for them to deploy an LLM that's secure. It's, with guardrails, et cetera, maybe longer. [00:04:52] Anush Elangovan: but you still have to go through the process and you have to be prepared to like, walk that walk to deploy an enterprises. That doesn't mean it's [00:05:00] not fast, that's as fast as you can do for that industry, right? And if you are deploying AI in healthcare, right, it's, it's got its own, uh, cycle. [00:05:07] Anush Elangovan: but in each one of these, you want to see how, like, go down to the essence of what is it that you actually have to do. And, you know, I, I, I like how you framed it. It's like it's, you shed your prior assumptions of how things are done, right. And, and you kind of build up from a, uh, first principles, uh, approach to say, this is how I could use AI to unlock, whatever I'm doing. [00:05:33] Anush Elangovan: And, and, some of it, you know, it's good to really step back and look at. Just question every part of it, right? Like right now you're getting chat GPT and, Gemini competing for like, math, olympiads and, and, uh, college, uh, reasoning, uh, tests. Right? And, and those are like that, that is amazing and increasingly like complex tasks that they're trying to do. [00:05:58] Anush Elangovan: But there may also be like. [00:06:00] More mundane things that AI could, could get applied to. Right? And, and so when we think about shedding old ways, you wanna shed it not just in like the tip of the spear. It's like, you know, I'm gonna see what's the frontier model. It's also, it could be something as simple as. [00:06:18] Anush Elangovan: How do you choose a, a movie, uh, you know, like a recommendation system, right? Or, or, uh, an automated, uh, flight, uh, rebooking system. So the moment, you know, your flight is late, uh, right now it's a notification, right? It's like, oh, you got a text message saying your flight's late. And I got that like three times this week. [00:06:38] Anush Elangovan: But anyway, uh, and, and, and, and, I was just like, okay, so if I were to rethink this. All this MCPs that we have that should be hooked up into an MCP that says, your flight's delayed. Here are your options. If you want, you know, these are the paid options. Yeah. Here are the free options. This will get you back into your you know, Toronto airport [00:07:00] tonight. [00:07:00] Anush Elangovan: Or if you stay, here's a hotel plus this, plus this, plus. It's just like, go ahead is all I should say. Versus now I'm like, okay, can someone, you know, can I call a travel agent? Can I do this? Can I go online and log into And you know, so we gotta fundamentally rethink even those like small, nuances of, things that we do that can be automated out and AI is really, really good at doing something like this, right? Maybe I just explained an AI startup idea right now. Somebody should just start that. [00:07:29] Andrew Zigler: I think you did. Yeah, you definitely did. Someone, one of our listeners is definitely going to lift that off of you. I, I, I, you know, I hate being on the receiving end of those. You feel a little helpless and then you have to like, follow the whole flow. So I know what you mean. Like I, I like how you called out that the build and this like. [00:07:45] Andrew Zigler: Where speed is your moat and the innovation layer is protecting you, is what makes you better than your competitors. How you scale that and you bring that to market. So by understanding the problems that you're solving, uh, throwing away those older assumptions, but also [00:08:00] recognizing that like. We're building every single day, new things and new ways of using stuff that we're still figuring out the implications of. [00:08:08] Andrew Zigler: And so when you have a lot of velocity and you're introducing a lot of new ideas, and maybe you have that workflow now that automatically rebook your flight off of your late flight text message, and uh, I know I would certainly use it, but you know, what kind of philosophies guide the way that y'all think about building this ecosystem to manage that stability while letting folks. [00:08:29] Andrew Zigler: Play with the speed and the assumptions and the airplane re bookings. [00:08:34] Anush Elangovan: so, so I think, you know, we need to peel one layer down, right? and the philosophy is, Hey, we, we just discovered electricity, right? And you know what we're gonna do? We are gonna make motors, uh, or dynamos, right? Like engines. Uh, sure. We don't know if it's gonna be a Ferrari that you're gonna make, or it's a a a a dump truck. [00:08:57] Anush Elangovan: That's good for doing this. But let's [00:09:00] let, which is also required, right? You need a dump truck. You need a garbage truck. And, [00:09:04] Andrew Zigler: Yeah. You need the [00:09:04] Anush Elangovan: course you need, uh, a Ferrari for a midlife crisis, right? So, [00:09:09] Andrew Zigler: precisely. [00:09:10] Anush Elangovan: But, but my, uh, point is what do we build next? And, uh, and this is what I meant by like, okay, let's, let's take those baby steps to build the. [00:09:20] Anush Elangovan: Infrastructure that's required that we know we'll have to use, right? So, so if I just discovered electricity, okay, great. Now one, how do I save this electricity and how do I use it? So there's battery technology, so you need to do something like that, right? Like so. But then you also want to make it into an actionable thing. [00:09:37] Anush Elangovan: You want to make it for like automobiles, or you wanna use it for, you know, powering, uh, entire cities. So it is that transformational. So, uh, AI is that transformational. So, if you distill down, it'll, it'll come down to how do we think about, what we can do with this this fundamental technology that, We may not be aware of what it [00:10:00] is gonna unlock next, but at least you know the next step is clear, right? It's like a dense fog, you know, it's gonna be like, it, it's the right path. You see the light, but it's kind of like out there and, and the steps you're taking are concrete and you're like, okay, this is good. [00:10:16] Anush Elangovan: I, this is better than where I was or where we were. So we are moving forward. So you can build with the. Intuition from what you see in the short term and a tactical view, but towards what you think the future is gonna be. [00:10:28] Andrew Zigler: Right. You almost like we're all in this like fog of war, right? And like you said, you're reaching out and you're trying to step through it. You could think of it too, as like you're in the dark and your hands are up in front of you and you know that. You're, you're not gonna run your face into a wall because your hands are out in front of you, but you're not gonna maybe do much better than that. [00:10:45] Andrew Zigler: So that's kind of like, I think the eco, the, the industry, the world that we find ourselves in, uh, and we all have to, then this becomes the power of an ecosystem, of a group of people working together to create that layer of, [00:11:00] uh, of establishing the [00:11:01] Anush Elangovan: exactly. And I, I, I just, instead of, you know, saying fog of war I describe it as like, you're in this. Beautiful valley with like a morning, uh, fog that's in. You can smell the flowers. You, you hear the birds. You are like, okay, it's, we are in like, uh, utopian paradise and yes, I just need to like, continue the walk, right? [00:11:24] Anush Elangovan: and then move forward with that, conviction that you're in the right spot. [00:11:27] Andrew Zigler: Yeah. So let's talk about that ecosystem world. This nice, I love how you describe it, this grassy side of a hill in the morning that's covered in some mist and maybe we can't see 30 feet in one direction, but it sure is a beautiful hill and it smells nice. And so we're all here. And why is, in that world, why is. [00:11:44] Andrew Zigler: You know, open source, their strategic advantage that y'all are going for in the AI hardware market. And, and then how does like ROCm turn that into wins for people within that ecosystem? [00:11:56] Anush Elangovan: you know, the, the way we look at it is this, is kind of like how I view [00:12:00] AI and the ecosystem, right? But, but it is for everyone to enjoy. Uh, and so we do want to make sure that. You know, it is, uh, beneficial for everyone. [00:12:09] Anush Elangovan: The ecosystem can come in and, and innovate. It's an open innovation engine. and uh, it is very different from, you know, having a walled garden with, Hey, only I know how to do this and I'm gonna do it and throw it over the fence and you can use it or keep walking, right? So we'd like to be good citizens that way, but also. [00:12:30] Anush Elangovan: Uh, it is self-fulfilling in a way, right? Like it, the, the pace at which we innovate with open source is unmatched. Like, you know, our serving engines are like VLLM and, and sg l. Those things, uh, those frameworks are like super, super aggressive in terms of how fast they come out with features and how fast they can you know, get performant models out. [00:12:52] Anush Elangovan: And that compared with what, uh, you'd get from, you know, the likes of like T-R-T-L-L-M or something is always lagging, right? Because you [00:13:00] just can't keep up with you know, 200 commits a week just on one particular model to get that model really performant [00:13:06] Andrew Zigler: And, and, and in that world where, you know, everyone can enjoy the winds of this, what kind of customer stories or innovation stories have really stood out to you and excite you about building and creating this place for developers? [00:13:19] Anush Elangovan: Yeah. So I think the parts that are super exciting for me are when when we get to see a customer that is first skeptical. Then they start a little like, okay, fine, we'll give you a chance. Uh, we do a simple, uh, POC and then they're like, huh, this seems to work. Yeah, we told you it works. [00:13:42] Anush Elangovan: You don't have to change one line of code. Really? Yes, no need to change one line of code. Okay, let's try a production workload. So then they try it. Oh, you're more performant than the competition. Yes. We're more performant than, than the competition. So how much does it cost? And we're like, oh, it's your TCO is better with, uh, [00:14:00] AMD. [00:14:00] Anush Elangovan: So again, they're like, wow, okay, good. So now how do we deploy at scale? And then we go deploy it at scale. And when they give a thumbs up on that and they say, this is good, right? That's when you know, you, you see it go full circle from like, oh, we, we've never heard about AMD to like actually deploy to tens of thousands of GPUs In the order of a few months, right? It, it, it really is fascinating to see and very exciting and invigorating to [00:14:28] Andrew Zigler: Yeah. At like a great exposure to a lot of interesting problems. And, and then people using the infrastructure, the, the technology available to solve those problems. Really specific problems by the way, that's often why they're bringing their data and AI to it, uh, is because it is really specific and important for them. [00:14:45] Andrew Zigler: And there's a, a lot I think that other engineering orgs can learn and even emulate from AMD's success and, and having this open source ecosystem and it causing this acceleration within. You [00:15:00] know, uh, customers and enterprises that use and adopt the tools and, and, and that creates an advantage. And that goes back to why we're talking and like the real thesis of our conversation today. [00:15:10] Andrew Zigler: So how do you think engineering leaders that are listening to this and obviously tapping into this great success AMD has from an open source flywheel, how do you think other, other folks building in the same space can foster that open, first, that open source oriented culture in order to, you know, accelerate their innovation goals? [00:15:29] Anush Elangovan: Yeah, that's a very good question. So the startup that um, was acquired by AMD we, we built, I mean, we started off doing iot stuff and you know, smart ring and all that, right? But in the, the end of like, uh, and not the end, the last six years of the company was building ML compilers. [00:15:47] Anush Elangovan: And ml, ML compilers are like super, uh, complicated, sophisticated, advanced algorithms, dah, dah, dah. but it was all open source, right? So our VCs were like, wait, what do you mean your core [00:16:00] IP is open source? And um, the speed is the moat applied even then, right? It was just like, yes, if you have an idea that. [00:16:08] Anush Elangovan: Because someone saw this idea that you are, they're gonna be able to catch up, then you probably have the wrong idea anyway. But if they are, you know, you execute and they're gonna catch up, that you should assume they're gonna catch up. Right? So you gotta move forward. So keeping it open source is super important. [00:16:25] Anush Elangovan: But also to your question on like, you know, the learnings from an AMD standpoint, right? If there are, hard problems, I'd say dig in and work through it, right? Like there's no way but through it, right? That should be the simple mentality. And more, uh, frequently than not. you'll see that you'll just make it through in a, in, in good form. [00:16:52] Anush Elangovan: But if you doubt it and you're like, oh, I don't know if I should commit, if I'm, I, you know, what should just commit to do the right thing [00:17:00] every step, right? Every step, and just keep taking one step in front of the other. And in no time you'll see that you'll be running. Right. And, and yes, the first few steps will be like, yeah, everyone's complaining about your software quality. [00:17:15] Anush Elangovan: Everyone's complaining about this and that, and it doesn't work. And, and a few steps in, you know, you get, you get the hang of all the complaints that are coming in. You get the feedback loop. You're like, okay, what, what are you prioritizing again? One step in front of the other, right? You just keep knocking that out and then you get to a point where you're, it just becomes second nature, right? To do the, to do the right thing. And, and then yes, if someone gives you two options, you'll be like, fine. This is, uh, you know, there's always the resource trade off. There's always a human capital trade off, but what's the right thing to do? of course, I, I'm pragmatic about what we choose, but, but if the right thing for your long-term success is dig in, go first, principles, make it [00:18:00] happen. [00:18:00] Anush Elangovan: Well. Then just go for that. There's, there is no shortcut to [00:18:04] Andrew Zigler: acknowledging, you know, how it aligns with your mission, your core company goals, and what you're looking to achieve. And, and I, I love how you rightfully called out that in the open source world and you know, you have your technology that you've built, what you think is your moat upon, right? [00:18:22] Andrew Zigler: It's your code and, and to open source that, or to just make it where anyone could peer in is, you know. Scary in one regard, but two, it just kind of feels like you're handing away your throne room in some kind of sense, a very direct feeling sense. But the ultimately, you were really right to call out, and this is something I think about all the time, that the real power there is still the speed This the speed. [00:18:42] Andrew Zigler: That was the moat at the beginning of our conversation. It's the speed in combination with your. Very specific domain understanding of what you're building and what you're creating, and your new role as the steward of that world and how people plug into it, which [00:19:00] has frankly, a lot more influence and power than lording over a closed. [00:19:04] Andrew Zigler: You know, repository or an ecosystem, and like you said, like throwing things over the wall. Sure. There, there might be people always on the other side of that wall, but you're not gonna have a great connection with them. You're not gonna be able to really clearly understand them. I, I like your metaphor of the side of the field of the mountain a lot more. [00:19:23] Andrew Zigler: But, but in the, in this world, you know, where. That speed is, is the power and, and open source is just one way that you can harness that speed to get really far ahead and to innovate. , There's other parts of this equation that you can be experimenting with too, and I'd love to pick your brain about them as a software leader and, and, and one of them is about looking forward and kind of understanding that future that we're all building towards and beyond today's models and hardware. [00:19:48] Andrew Zigler: You know, what do you see as the next major bottleneck or opportunity in the AI compute space? As, as you know, enterprises and folks start to get a little more mature about what's available to [00:20:00] them. [00:20:00] Anush Elangovan: Yeah, I think, the bottleneck and opportunity is, uh, what I'd call, call walking the last mile of ai. Right. Uh, and like I I, I gave you an example, uh, previously, but, but it's similar to that. It's like there are cases where Humans have so many, uh, things to do in your day. You know, like the, if we sit down and actually had a customer focus like, okay, these customers lives, I'm gonna save four hours of this customer's life. And if you actually sit down and look at all of that, it'll be. Easily automatable, easily you know, uh, applicable, uh, for ai, right? [00:20:39] Anush Elangovan: Like, but then making it happen is gonna take a little bit, right? It's like maybe it's, uh, paying your utility bill, right? Or something like that, right? Or, or, your healthcare explanation of benefits. Uh, like, I'm sure you get an explanation of benefits, and I'm like, I, I don't even know what that thing is. [00:20:55] Anush Elangovan: It's just like EOB and like. [00:20:57] Andrew Zigler: it's a big, a big old PDF. Yeah, [00:21:00] exactly. [00:21:01] Anush Elangovan: Like, like, I'm like great straight to the, uh, shredder, right? And but that could be, you know, automated with the ai, right? It, it, it'd be like, Hey, the summary of this thing is you went and visited this day. Everything is okay. Everything is paid for, so don't worry, it's not a bill. [00:21:17] Anush Elangovan: That again, the same, uh, thing, but the sense of what that information overload is could be. Digested by ai, uh, accumulated over time and retrieved when you need it. Like, I don't, I actually don't even need to know this EOB right now, unless of course, whenever I need to know it, that maybe, you know, like for some benefits I need to figure out what do, what did I do over the past year and how do I apply it? Source:

Mike

14,195 görüntüleme • 8 ay önce

Apple’s iPad “Crush” Ad Is Bleak, Ominous and Threatening I don’t know if you’ve seen Apple’s just-released commercial for the “New” iPad Pro, but it’s pretty awful. It is dark, humorless, and feels like a not-so-thinly veiled threat to writers, musicians, game makers, developers, and artists of all kinds. …and children, even. I’ve watched it at least five times today alone, and I’m left with one big question. “Who on earth approved this?” It’s absolutely baffling that the world’s largest technology company, with the world’s biggest marketing budget, thought this would be a good idea. What kind of idiot—or idiots, since dozens or hundreds of people had to be involved in the writing, staging, producing, recording, and editing—felt this kind of ad would somehow create a positive emotional connection with consumers? Seriously, it’s terrifying. In a dank, cold warehouse, devoid of all life and humanity, an industrial crusher comes to life, and slowly starts destroying a collection of musical, philosophical, and artistic devices and instruments. For no apparent reason, everything starts getting smashed: first, a trumpet, then an arcade video game, then cans of paint, a piano, a globe, a metronome, a guitar… on and on it goes, obliterating everything in sight into a colorful, gooey, explosive mess. Books, camera lenses, lamps, a guitar, a sculpture, and a typewriter—all tools of the liberal arts—get mangled into a garbage heap as Sonny & Cher cheerfully sing, “All I ever need is you.” In the penultimate moment, a goofy yellow smiley emoji becomes a bug-eyed scary-clown freak as it, too, is crushed to death. Worse, if you enable closed captions like I do by default, the video says: “[POPPING] [SPLAT]” right as its eyeballs pop out of its head when Cher sings, “Give me a reason to build my world around you.” It’s enough to make a child cry. It has all the comforting vibes of the burnt pink teddy bear floating in the swimming pool on Breaking Bad after two planes crash in mid-air. I have so many questions (aside from simply wondering the names of the soon-to-be ex-employees who greenlit this abomination). First of all, as a trumpet player myself, I am personally offended that they made me watch a perfectly good trumpet get smashed to smithereens like it’s no big deal. Why would they torture me like this? Second of all, what is the message here? No, not that “the most powerful iPad ever is also the thinnest,” as the voiceover artist states in the last few seconds of the clip. I mean: what is the message? Ostensibly, pulverizing children’s toys, arcade games, architectural models, and ceramic Angry Birds into a paste implies something like “We’re taking all the best of humanity; all the collective works of Western Civilization, smashing it into pieces and putting it inside this remarkably thin device so you can have all of it in the palm of your hand.” But my oh my, is there an elephant in this room… he’s hiding behind the monstrous destroying machine. Did anyone inside Apple realize that everyone outside Apple will recognize this imagery in a metaphorical sense, but not the one Apple intended? We don’t see a crushing machine gently consolidating the greatest output of all our artistic endeavors, simply reformatted for a digital age and consumed by everyone with instant, fingertip access. We see what is painstakingly obvious to us, and the timing couldn’t possibly be worse. We see a giant, soulless machine consuming our work in a very different way. Right now, AI models are training themselves on our intellectual property and even our very own personally-identifying data. We aren’t the ones doing the consuming. We’re the ones being consumed. The tech industry has become one massive gaping maw, opening wide and swallowing everything in sight, chewing it up into little bits and pieces of comminuted waste, like a paper shredder or a garbage disposal. It’s destruction in its most literal form. And for what? For a newer version of the iPad that is only slightly thinner than its predecessor? For an only marginally improved version of Apple’s tablet device that has been around for 14 years? For increased profits? This is a terrible look for Apple. They may as well be saying: “All your work are belong to us.” Personally, I am a fan of artificial intelligence. I am eagerly embracing our robot overlords and I welcome our new CSV god (as the actual developers of AI models like to say). I look forward to the freedom and innovation that will come as a result of humanity augmenting our intelligence with AI like a force multiplier on a battlefield. But if Apple has the same perspective I do, they’re selling it in the worst possible way. When I see this video, I see that Apple is definitely crushing something… but I’m not sure what. -Crushing small companies that develop apps for the extremely heavy-handed App Store, which imposes byzantine restrictions on what they can and can’t do with their own apps? -Crushing competitors by limiting what they can do on the iOS and MacOS platforms with arbitrary and capricious rules about enabling functionalities that Apple doesn’t like, even if users do? -Crushing publishers and content creators with a punitive 30% fee on all subscriptions and in-app purchases? -Crushing choice and competition by not allowing app makers to make apps and programs that do the same thing that native apps already do, even if they do it better? -Crushing all human creativity and innovation by automating and systematizing everything? In the early days of the “Google vs. Apple” fight over the web and app stores, I was really concerned that Google was becoming way, way too powerful. Specifically, in 2015, when Google came up with “app streaming,” they announced a desire to form a “web of apps.” This was concerning. Especially when coupled with Google’s efforts to steal content from other websites and provide it to users via the “knowledge graph” results, ending up with the creation of “zero-click” search results pages, which absolutely punished website owners and content creators. By taking the most valuable content off a website and showing it to Google users without them needing to click through to the website itself, Google had essentially stolen everybody’s intellectual property with only the most minimal attribution possible (to fend off lawsuits no doubt, but with no intention of users actually visiting the website in question anymore). “Google is eating the internet,” I thought, and said out loud, (although I probably wasn’t the first person to use that phrase) But what I meant was purely an analogy. It was vague and ambiguous, almost silly. Maybe I was wrong, though: maybe it’s Apple that’s doing the eating. Maybe Apple is not only gobbling up everyone else’s work, but also homogenizing it—and us—and forcing us to use their platform, pay their fees, abide by their rules, and constantly keep upgrading, upgrading, upgrading, to an ever-thinner iPad in order to use it. Watch the video again. This is the stuff of nightmares. To be perfectly fair, even if I were to take the commercial at face value and ignore it’s off-the-charts creepiness and just stick to its one stated claim—that the new iPad Pro is thinner—it still fails as a commercial. Why? Because nobody cares how thin an iPad is. Seriously. I’ve owned an iPad since 2010: that means I’ve carried around a version of Apple’s already-thin tablet every day for over a dozen years. Never once have I said to myself: “You know what improvement I’d really like to see in this thing? I wish it were thinner.” Never. That thought has never crossed my mind, even once. You know what has? -Better battery life. -I’d like my iPad to not get hot to the touch when I use the Apple Pencil to take notes. -I wish it wasn’t so fragile: I dropped my brand-new iPad 2 back in the day when it slipped out of the arm-hold I was carrying it in, it bounced on the pavement, and the screen shattered into a thousand pieces, making it unusable. -I wish it had more storage. -I wish Apple would stop changing the type of cable connector it uses: I’ve gone from the original 30-pin connector to the Lightning connector, and now to the current USB-C/Thunderbolt connector. -I wish I could view the screen in direct sunlight. -I wish it wouldn’t overheat and turn off automatically when I use it outdoors in the summertime. Those are announcements I would welcome in a new iPad Pro commercial. None of this “now even thinner” nonsense nobody needs or cares about. So, back to the commercial. In my opinion, whoever made this ad should be fired. I almost never say that about other companies, especially for good-faith marketing efforts gone wrong… those of us who work in marketing make mistakes sometimes, and we learn from them. But cases like this warrant a special exception. Marketing and advertising are designed to make people want to buy your products. This commercial doesn’t just not make me want to buy Apple’s products. It makes me not want to buy Apple’s products, which is something altogether different. It turns me from someone who likes iPads into someone who is almost rethinking iPads entirely. That’s not just a bad advertisement; it’s a harmful advertisement. Apple’s usually known for great commercials. The legendary 1984 Super Bowl commercial was, of course, their best. I thought “Hello, I’m a Mac” was absolutely brilliant. They have made some missteps along the way, but this one is really bad. Not even their nauseatingly preachy and woke “Mother Nature” ad from a few years ago was this bad. Steve Jobs once said, “Technology alone is not enough—it’s technology married with liberal arts, married with the humanities, that yields us the results that make our heart sing.” My goodness, that last line alone is poetry itself! This ad seems to be Apple signaling that they don’t believe in that anymore. And I don’t think all this handwringing is an overreaction to where you could say “Oh, c’mon, it’s just a commercial! What’s the big deal?” It is a big deal. It tells you about the values of the company, and what they intend to communicate. Really, how is this the same company that used to sell iPhones by showing grandmas using FaceTime to connect with their baby grandchildren from afar during the holidays? Everything about it is wrong: even the thumbnail they chose for it (the bulging-eyed smiley face) and the fact that they gave it the title “Crush!” It was fun to see the reactions to the video online today. I find it fascinating that Apple shared it on YouTube but turned off the comments. On X, Tim Cook shared it Tuesday, and the video, which so richly deserves to be mocked, is getting it in spades. Some people are calling it “anti-art.” One user called it “soul-crushing,” which was about as literal and logical a response as you’d expect. It turns out Apple actually made an announcement about the commercial. In response to the (apparently unexpected) poor welcome it got, Apple wrote: “We missed the mark with this video, and we’re sorry.” Lame response from a tone-deaf tech behemoth, but still, they hopefully got the message. C’mon, Apple. I have seen the future, and this ain’t it.

Ron Stauffer

19,249 görüntüleme • 2 yıl önce

CANCEL Your Weekend Plans, and Learn Claude Code Today. $5,000/month. $10,000/month. $20,000/month. People are building entire apps and charging clients thousands using Claude Code. You're still Googling 'how to center a div.' While you're binge-watching a show you won't remember next week, a 19 year old with zero coding experience just built a $5,000 SaaS product in one afternoon using the tool I'm about to break down. Same laptop. Same internet. Same 24 hours. He has Claude Code. You have Netflix. That's the only difference. This YouTube video is a goldmine. Full Claude Code tutorial. Beginner to pro. Every feature. Every setup step. Every best practice. Zero prior knowledge needed. Save it. Watch it tonight. Not tomorrow. Tonight. Save this post. This is your complete Claude Code roadmap. Lose it and you lose the next 12 months of income. Follow Himanshu Kumar so you don't miss the breakdowns for each feature. ↓ 1. Understand What Claude Code Actually Is. You think Claude Code is just another chatbot. It's not. And that misunderstanding is why you're broke. ChatGPT gives you text. Claude Code gives you software. It runs in your terminal. It reads your entire codebase. It writes files directly to your project. It runs commands on your machine. It debugs errors autonomously. It builds features end to end. You're not chatting. You're deploying a developer. One that works 24/7. Never asks for a raise. Never calls in sick. Never pushes broken code at 5 PM on a Friday. People are charging clients $5,000-$10,000 for apps they built with Claude Code in 3 hours. And you didn't even know this tool existed because you're still asking ChatGPT to write you a to-do list. The gap between you and people making money with AI isn't intelligence. It's awareness. Now you're aware. Save this post. Follow Himanshu Kumar for the complete breakdown of every Claude Code feature. ↓ 2. Set Up Claude Code Properly. Most people quit here. "It's too complicated." "I don't know terminal." "I'll set it up later." Later never comes. And "complicated" means "I watched for 30 seconds and gave up." The setup takes 10 minutes. Install Node.js. Install Claude Code via npm. Authenticate your account. Open your terminal. Done. 10 minutes. You spent longer this morning deciding what to have for breakfast. The video walks through every single click. Every command. Every screen. Assuming you know absolutely nothing. If you can download an app on your phone, you can set up Claude Code. It's the same level of difficulty. But you'll still tell yourself it's "too technical" because that excuse is more comfortable than admitting you're just scared to try something new. This is the setup that everything else builds on. Skip it and nothing works. ↓ 3. Use the Desktop App. You don't even need to live in the terminal if you don't want to. Claude Code has a desktop app. Clean interface. Visual feedback. Everything you need without touching command line. But here's the thing most people don't know: The desktop app isn't just a pretty wrapper. It lets you manage projects visually. See file changes in real time. Switch between projects instantly. The people making money with Claude Code use the desktop app for client projects because it's faster to manage multiple builds simultaneously. You're still opening 14 browser tabs to organize one project. They open one app and everything's there. Efficiency isn't a personality trait. It's a tool choice. Save this post. Follow Himanshu Kumar for the desktop app workflow that handles 5 client projects at once. ↓ 4. Install the Right Dependencies. This is where beginners silently fail and blame the tool. Claude Code needs certain dependencies installed to work properly. Miss one and everything breaks. Then you go on Twitter and say "Claude Code doesn't work." It works fine. You just didn't read the setup guide. The video covers every dependency you need. What to install. How to install it. How to verify it's working. No guessing. No Stack Overflow rabbit holes at midnight. No "why isn't this working" for 3 hours. Watch the dependency section once. Follow every step. Never deal with setup issues again. You spent more time last week troubleshooting a printer than this takes. ↓ 5. Work Inside Your Code Editor. Claude Code integrates directly with your code editor. VS Code. Cursor. Whatever you use. It's not a separate window you alt-tab between. It's right there. In your workflow. You type a request. Claude writes the code. The code appears in your editor. You review it. Accept it. Done. No copy pasting between windows. No reformatting code that got mangled in transit. No "which version was the right one." It's like pair programming with someone who never gets distracted, never argues about naming conventions, and actually writes code that works on the first try. Your current coding process is: Google the problem, read 5 answers on Stack Overflow, copy the wrong one, debug for an hour, find the right one, paste it in, break something else, repeat. Claude Code's process is: describe what you want, get working code, move on with your life. Same hour. One method produces working software. The other produces frustration and a browser history full of Stack Overflow tabs. Stop coding the hard way. Save this post. Follow Himanshu Kumar for code editor setup guides and integration tips. ↓ 6. Master Basic Usage. Most people learn 5% of a tool and say they "know" it. You "know" Photoshop because you can crop an image. You "know" Excel because you can sum a column. You "know" Claude Code because you asked it one question. Basic usage means: How to give Claude Code context about your project. How to ask for changes to existing code. How to generate new files and features. How to review what Claude produces. How to iterate when the output isn't perfect. These basics are the foundation of everything. Skip them and every advanced feature feels confusing. Master them and every advanced feature feels obvious. The video breaks down each one with real examples. Not theory. Actual usage on actual projects. You've been using AI tools at 5% capacity and wondering why your results are 5% of what others get. Save this post. Follow Himanshu Kumar for daily Claude Code usage tips. ↓ 7. Learn Every Command. Claude Code has commands that most users never discover. Because most users type one message and expect magic. That's not how professionals use it. Professionals use specific commands that tell Claude Code exactly what to do, how to do it, and what constraints to follow. The difference between a beginner and someone making $10K/month with Claude Code is knowing which command to use and when. The video walks through every single one. Not just what they do. But when to use each one. And why one command is better than another for specific situations. You've been using Claude Code like a hammer. These commands turn it into a full toolbox. Stop treating a power tool like a blunt instrument. Save this post. Follow Himanshu Kumar for the command cheat sheet I use daily. ↓ 8. Understand Modes and Shortcuts. Speed matters. The person who builds an app in 2 hours charges $5,000. The person who builds the same app in 2 days charges $2,000. Same app. Same quality. Different speed. Different income. Claude Code has modes that change how it operates. And shortcuts that cut your workflow time in half. Most people don't know either exists. They use Claude Code in default mode for everything. Like driving a car in first gear on the highway. Technically it works. But everyone is passing you. The video shows you every mode. Every shortcut. Every time-saving trick that separates the people charging $2,000 per project from the people charging $10,000. Speed is money. Literally. Save this post. Follow Himanshu Kumar for the shortcuts that cut my build time by 60%. ↓ 9. Write a Proper Planning Prompt. This is the section that separates amateurs from professionals. And it's the section most people skip. A planning prompt tells Claude Code what you're building before you start building it. Architecture. File structure. Technologies. Features. Constraints. Edge cases. Without a planning prompt, Claude Code guesses. And guessing produces garbage. With a planning prompt, Claude Code executes a clear plan. And clear plans produce working software. The video shows you exactly how to write a planning prompt that makes Claude Code produce professional-grade output on the first try. "But I just want to start coding." That's why your code breaks every time. That's why you restart projects 4 times. That's why nothing you build ever gets finished. Because you refuse to plan. A 5-minute planning prompt saves you 5 hours of debugging. But you'd rather skip the 5 minutes and suffer through the 5 hours because patience isn't your thing. And that's exactly why you're not making money. Planning is the most underpaid skill in coding. And the most overpaid when you master it. Save this post. Follow Himanshu Kumar for the planning prompt templates I use for every client project. ↓ 10. Choose the Right Model. Claude Code lets you select different AI models. Not all models are the same. Not all tasks need the same model. Using the most powerful model for a simple task wastes credits. Using a basic model for a complex task wastes time. The video explains: Which model to use for quick fixes. Which model to use for complex architecture. Which model to use for debugging. Which model to use for code generation. Most people pick one model and use it for everything. That's like using a sledgehammer to hang a picture frame. Model selection is strategy. And strategy is money. The people making $10K/month with Claude Code are strategic about every credit they spend. You're burning through credits because you use the most expensive model to write a hello world. ↓ 11. Use Git and Version Control. If you're not using version control, you're one mistake away from losing everything. Claude Code integrates with Git. Every change tracked. Every version saved. Every mistake reversible. Without Git: Claude makes a change. It breaks something. You can't undo it. You start over. 3 hours wasted. With Git: Claude makes a change. It breaks something. You roll back in 5 seconds. Keep working. Version control isn't optional. It's insurance. And the people not using it are the same people who say "I lost my entire project" like it's something that just happens. It doesn't just happen. It happens because you didn't set up Git. The video walks through the entire Git integration. Save this post. Follow Himanshu Kumar for the Git workflow that's saved every project I've ever built. ↓ 12. Set Up Claude.MD and Memory. This is the feature that makes Claude Code feel like a real team member instead of a stranger you explain everything to every time. ClaudeMD is a memory file. You tell Claude Code about your project once. It remembers forever. Coding style preferences. Project architecture decisions. Technology stack. File naming conventions. Business logic rules. Without ClaudeMD: Every new conversation starts from zero. You explain the same things repeatedly. Output is inconsistent. With ClaudeMD: Claude knows your project. Claude follows your rules. Claude produces consistent, professional code. The difference between a sloppy freelancer and a reliable agency is consistency. Claude. MD gives you consistency without the agency overhead. Most people don't set this up and wonder why Claude Code gives different answers every time. ↓ 13. Automate with Tasks. This is where Claude Code stops being a tool and starts being an employee. Tasks let you define repeating workflows. "Every time I push code, run tests." "Every time I create a new file, add boilerplate." "Every time I start a session, check for errors." Automated. Hands-free. Consistent. You're doing these things manually every single day. The same checks. The same steps. The same routine. Tasks do them automatically. So you can focus on the work that actually makes money. Every manual task you automate is time you get back. And time is the only thing you can never make more of. Save this post. Follow Himanshu Kumar for the task automation templates that run my entire workflow. ↓ 14. Explore Features Most People Never Touch. The video covers features that 95% of Claude Code users don't know exist. Because they watched a 3-minute TikTok about Claude Code and think they're experts now. They're not. They're using 5% of a tool that can do everything. The full tutorial goes deep into features that most tutorials skip because they're "too advanced." They're not too advanced. They're too valuable for lazy creators to bother explaining. This video explains all of them. Clearly. For beginners. The 5% of features you don't know about are the 5% that make people rich. ↓ Let's zoom out. I just broke down 14 sections of Claude Code. Setup and installation. Desktop app. Dependencies. Code editor integration. Basic usage. Commands. Modes and shortcuts. Planning prompts. Model selection. Git and version control. Memory and Claude. MD. Tasks and automation. Advanced features. All in one video. All free. All beginner friendly. The person who masters even half of these in the next 2 weeks will be in the top 1% of Claude Code users. The top 1% of Claude Code users are the ones charging $5,000-$10,000 per project and building them in a single afternoon. Everyone else is asking ChatGPT to fix their resume. Same tools. Same access. Completely different outcomes. Because one person treats AI like a toy. And the other treats it like a business. ↓ Here's the hard truth nobody wants to hear. You don't have a talent problem. You don't have an intelligence problem. You don't have a resources problem. You have an action problem. Everything I just listed has a free tutorial right here in the attached video. 33 minutes. That's it. 33 minutes to learn the tool that people are using to build $5,000-$20,000/month businesses. You spent more time today scrolling Twitter than it takes to watch this video. You spent more time this week watching Netflix than it takes to master Claude Code basics. You spent more time this month doing nothing than it would take to completely change your income. The information is free. The tool is accessible. The opportunity is here. The only thing missing is you caring enough to start. ↓ CANCEL your plans this week. This isn't optional anymore. The people learning Claude Code right now will be building apps for the people who didn't learn it. That's not a prediction. That's already happening. Companies are replacing $150/hour developers with one person and Claude Code. If you code: learn Claude Code or become half as valuable by next year. If you don't code: learn Claude Code or miss the biggest opportunity to start earning from tech without a CS degree. There's no path forward that doesn't include AI coding tools. None. You have one window. Right now. This week. ↓ Here's your action plan for the next 7 days: Day 1: Watch the full video. Install Claude Code. Set up dependencies. Day 2: Learn basic usage. Try 5 different commands. Day 3: Write your first planning prompt. Build a small project. Day 4: Set up Claude. MD. Configure your memory file. Day 5: Master modes and shortcuts. Build a second project faster. Day 6: Set up Git integration. Automate with tasks. Day 7: Build something real. A tool, an app, a website. Ship it. 7 days. One tool. One completely different skill set. One completely different income potential. Or 7 more days of scrolling Twitter watching other people build things while you "plan to start." Your call. ↓ This is the most important video you'll watch this year. 33 minutes. Complete Claude Code mastery. From zero to building real projects. Save this post. Come back to it every single day this week. Check off each section as you complete it. Follow Himanshu Kumar for daily Claude Code breakdowns, advanced tutorials, and the exact workflows that are turning beginners into $10K/month builders. The only thing between you and $10K/month with Claude Code is this video and 7 days. Don't waste them. You Must Follow me Himanshu Kumar, so i can send you DM.

Himanshu Kumar

101,793 görüntüleme • 4 ay önce

"If you have the facts and the law on your side, you don't need to pound the table, Mr. Bederow!" Here's my overview as to why Robert Cosgrove stalling for months to get a protective order for Lindsey Gaetani's phone extraction (that Brian Tully leaked, unredacted, after only removing messages from Tully to Lindsey and from PI Kate Peter to Lindsey) is Aidan Kearney's strongest argument for Cosgrove's recusal. I am not a lawyer. This is not legal advice. I am a towel. TRANSCRIPT: Before Ms. Gaetani accused him of intentional misconduct, Mr. Cosgrove successfully fought to prevent the public release of embarrassing and private details from her personal life by seeking broad impoundment and protective orders. No, no, no, no, no, no, no. I don't care if you weren't on the case at that point - you don't get that wrong. I'm sorry, I have to object on fact. Olivia, that is not what happened. Olivia prides herself on a knowledge of the factual record. Olivia, that is not what happened. You wanna know what happened? You want me to lay it out for you? I'll do it. April 2024. Brian Tully, personally --well, Ken Mello is in the hospital-- takes a 15-year unredacted extraction of Lindsey Gaetani's cell phone, compared to Natalie, who was allowed to submit her cell phone to a private company and remove things before Tully got the extraction of Natalie's phone. Ms. Hoity-Toity over there. Fuck your aristocracy, fuck your Hollywood, fuck yourself. Anyway, so Tully, in all his infinite fucking wisdom, removes messages from Kate Peter to Lindsey and from Tully to Lindsey before leaking this extraction while Ken Mello's in the fucking hospital. Then Ken Mello invokes the clawback provision of the discovery rules in Bradl's—like, I'm Tim Bradl. He was being Tim Bradl. As much as I blame Aidan and Tim Bradl for being Aidan and Tim Bradl, they were just proxies here. Folks, Tully was the mastermind and Jason Broyles was the intended recipient so that Broyles could attack Lindsey and myself to get credibility with Turtle Riders, to get close to Aidan so he could feed intel back to Kate and Tully, in my opinion. Anyway, the point is, that's in April. Tully doesn't even return Lindsey's call for like six days and then he's like, eh, meh. Of course he was like, meh, because he's a motherfucker, in my opinion. I mean, not lovingly. So anyway, this motherfucker goes about his business, doesn't give a fuck. Cosgrove doesn't do fucking shit until September of 2024. And he knows it. And everybody knows it. That motherfucker goes into court - oh, I get in a mood about this. That motherfucker goes into court in September of 2024 and fucking writes a handwritten fucking protective order, being like, oh, it's okay if Aiden keeps a copy of the phone and et cetera, et cetera, et cetera. That was in front of Judge Squires Lee. That was the same day that Lindsey got sabotaged at the courthouse by a court clerk...no comment. I love most of those clerks. They're wonderful. I love the court officers. I don't like what happened that day. I don't like it at all. Anyway, so I go in there -- wait a minute, what were we talking about? Oh, right. I think I was watching court that day. I was either watching or there, and Lindsey is there and Tully's -- Cosgrove's there and Bradl's there. And Judge Squires Lee is like, ah, you know, go write the agreement. So Cosgrove and Bradl write it by hand and file it. Fucking bullshit. You know how I -- now I'm not saying Judge Squires Lee did anything wrong. I think the clerk kind of misled her because she was in the bag for Jen McCabe, which is a whole different story. But the point is, so the one thing that Judge Squires Lee did that made me realize that I think she caught on to the fact that the clerks fucked around was that Judge Squires Lee entered an order on the docket permanently allowing Lindsey to file pleadings. So anytime Lindsey could just go in and they'd be like, no - -Lindsey could be like, I have an order from Judge Squires Lee. It was the strangest thing. Anyway, so that kind of-- but I don't really know what to make of all that. Anyway, so it's bullshit though. That is wrong from Bederow. And I'll tell you why: because it wasn't until Lindsey made a motion, okay, about this protective order that Judge Krupp on December 27th, 2024, spanked Brian Tully and Robert Cosgrove and Aiden a little bit. And it was --I'm paraphrasing here, Judge did not say the word motherfucker-- and it was like you motherfuckers. You got to read that three-page order from Judge Krupp from December 27th. You want to say Robert Cosgrove --no, Mr. Bederow-- no. And what's weird is there's no reason to present it this way, okay? Because presenting it the way that is true to the factual record and in the way I just described buttresses your argument that Cosgrove was conflicted because he tried to let the phone extraction go unprotected for months. Hello? Feel like I'm fucking banging my head against the wall sometimes with these fucking lawyers. Sorry, I shouldn't add this coffee, I'm in a mood. The point is, no. That's wrong, factually. And the factual record makes your argument stronger. Oh my god. Oh my god. How can - how can you get it so wrong and hurt your own argument at the same time? If you're gonna get it fucking wrong, get it wrong because the truth hurts your argument. If you have the truth and if you have the facts on your side and the law on your side, you don't have to pound the table. Just state it correctly. Cosgrove sabotaged the attempts to get a protective order on the phone, and five months after the phone was released by Tully --mind you-- Cosgrove is delaying to protect Tully, because Tully edited the extraction because he wanted it to be released right when the first Karen Read trial started, so that all the Turtle Riders would focus on Lindsey. And I'll tell you, there's something to be said here. There's something to be said about how even Bederow doesn't get it. Because Cosgrove doing that—waiting months to do the first bullshit protective order, and then not doing anything to get Judge Krupp to issue a protective order—it was Lindsey who got Judge Krupp to do that. Well, it was Judge Krupp realizing, I think, what had happened. Judge Krupp, when he retires, I want to talk to him about that day. I want to be like, did you—how pissed were you when you realized that Tully did this on purpose? I'm dropping like, oh that went fine. Judge Krupp is a stern judge too. You know what, I'm gonna get on his bad side. If you're on his good side, you might get a smile and a little chuckle. And then he's right into it. If you're on his bad side, he will not let you talk. I love judges like that. All right, let's continue. So it's like, my God, go to federal court. If you get a smile from Judge Talwani, that is like a core memory. I got a smile from Judge Talwani. I just beamed. Now, she did put a court sign on her courtroom being like no loud typing before I got there. So I knew she knew I was coming. It was for the Leslie hearing. But she still smiled at me. But anyway, this is wrong. I just want to tell you that on page 10 of 22, paragraph --second full paragraph, lines one through four-- it's just wrong. And Bederow should make the argument stronger by pointing out that Cosgrove was hostile to Lindsey and therefore had a bias against her long before any of this went down. Cosgrove was protecting Tully and Kate Peter from the beginning. There's a pattern. Cosgrove also hid that email from Kate Peter to Ken Mello. We're going to read it at the end of this. Come on, breathe. Bederow. Is this what all New York Jets fans are like? Aren't you a Patriots fan, motherfucker? I was going to say his life would really suck if he's a Jets fan. But if he's a Pats fan - now I remember he wears Pats sweatshirts. Come on, Mr. Bederow. Think like Tom Brady. His view apparently changed. No, it did not. No, it did not, Mr. Bederow.

Grant Smith Ellis

13,885 görüntüleme • 7 ay önce

CANCEL Your Weekend Plans, & Learn Claude Code Today. This Claude Code teaches more about vibe-coding in 30 mins than most tutorials do in hours. Save this, it'll change how you build forever People are building entire apps and charging clients $5,000 to $20,000 using Claude Code. This Claude Code video is a goldmine. Full Claude Code tutorial. Beginner to pro. Every feature. Every setup step. Every best practice. Zero prior knowledge needed. Save it. Watch it tonight. Not tomorrow. Tonight. Follow Himanshu Kumar so you don't miss the breakdowns for each feature. This is your complete Claude Code roadmap. Lose it and you lose the next 12 months of income. ↓ 1. Understand What Claude Code Actually Is. You think Claude Code is just another chatbot. It's not. And that misunderstanding is why you're broke. ChatGPT gives you text. Claude Code gives you software. It runs in your terminal. It reads your entire codebase. It writes files directly to your project. It runs commands on your machine. It debugs errors autonomously. It builds features end to end. You're not chatting. You're deploying a developer. One that works 24/7. Never asks for a raise. Never calls in sick. Never pushes broken code at 5 PM on a Friday. People are charging clients $5,000-$10,000 for apps they built with Claude Code in 3 hours. And you didn't even know this tool existed because you're still asking ChatGPT to write you a to-do list. The gap between you and people making money with AI isn't intelligence. It's awareness. Now you're aware. Save this post. Follow Himanshu Kumar for the complete breakdown of every Claude Code feature. ↓ 2. Set Up Claude Code Properly. Most people quit here. "It's too complicated." "I don't know terminal." "I'll set it up later." Later never comes. And "complicated" means "I watched for 30 seconds and gave up." The setup takes 10 minutes. Install Node.js. Install Claude Code via npm. Authenticate your account. Open your terminal. Done. 10 minutes. You spent longer this morning deciding what to have for breakfast. The video walks through every single click. Every command. Every screen. Assuming you know absolutely nothing. If you can download an app on your phone, you can set up Claude Code. It's the same level of difficulty. But you'll still tell yourself it's "too technical" because that excuse is more comfortable than admitting you're just scared to try something new. This is the setup that everything else builds on. Skip it and nothing works. ↓ 3. Use the Desktop App. You don't even need to live in the terminal if you don't want to. Claude Code has a desktop app. Clean interface. Visual feedback. Everything you need without touching command line. But here's the thing most people don't know: The desktop app isn't just a pretty wrapper. It lets you manage projects visually. See file changes in real time. Switch between projects instantly. The people making money with Claude Code use the desktop app for client projects because it's faster to manage multiple builds simultaneously. You're still opening 14 browser tabs to organize one project. They open one app and everything's there. Efficiency isn't a personality trait. It's a tool choice. Save this post. Follow Himanshu Kumar for the desktop app workflow that handles 5 client projects at once. ↓ 4. Install the Right Dependencies. This is where beginners silently fail and blame the tool. Claude Code needs certain dependencies installed to work properly. Miss one and everything breaks. Then you go on Twitter and say "Claude Code doesn't work." It works fine. You just didn't read the setup guide. The video covers every dependency you need. What to install. How to install it. How to verify it's working. No guessing. No Stack Overflow rabbit holes at midnight. No "why isn't this working" for 3 hours. Watch the dependency section once. Follow every step. Never deal with setup issues again. You spent more time last week troubleshooting a printer than this takes. ↓ 5. Work Inside Your Code Editor. Claude Code integrates directly with your code editor. VS Code. Cursor. Whatever you use. It's not a separate window you alt-tab between. It's right there. In your workflow. You type a request. Claude writes the code. The code appears in your editor. You review it. Accept it. Done. No copy pasting between windows. No reformatting code that got mangled in transit. No "which version was the right one." It's like pair programming with someone who never gets distracted, never argues about naming conventions, and actually writes code that works on the first try. Your current coding process is: Google the problem, read 5 answers on Stack Overflow, copy the wrong one, debug for an hour, find the right one, paste it in, break something else, repeat. Claude Code's process is: describe what you want, get working code, move on with your life. Same hour. One method produces working software. The other produces frustration and a browser history full of Stack Overflow tabs. Stop coding the hard way. Save this post. Follow Himanshu Kumar for code editor setup guides and integration tips. ↓ 6. Master Basic Usage. Most people learn 5% of a tool and say they "know" it. You "know" Photoshop because you can crop an image. You "know" Excel because you can sum a column. You "know" Claude Code because you asked it one question. Basic usage means: How to give Claude Code context about your project. How to ask for changes to existing code. How to generate new files and features. How to review what Claude produces. How to iterate when the output isn't perfect. These basics are the foundation of everything. Skip them and every advanced feature feels confusing. Master them and every advanced feature feels obvious. The video breaks down each one with real examples. Not theory. Actual usage on actual projects. You've been using AI tools at 5% capacity and wondering why your results are 5% of what others get. Save this post. Follow Himanshu Kumar for daily Claude Code usage tips. ↓ 7. Learn Every Command. Claude Code has commands that most users never discover. Because most users type one message and expect magic. That's not how professionals use it. Professionals use specific commands that tell Claude Code exactly what to do, how to do it, and what constraints to follow. The difference between a beginner and someone making $10K/month with Claude Code is knowing which command to use and when. The video walks through every single one. Not just what they do. But when to use each one. And why one command is better than another for specific situations. You've been using Claude Code like a hammer. These commands turn it into a full toolbox. Stop treating a power tool like a blunt instrument. Save this post. Follow Himanshu Kumar for the command cheat sheet I use daily. ↓ 8. Understand Modes and Shortcuts. Speed matters. The person who builds an app in 2 hours charges $5,000. The person who builds the same app in 2 days charges $2,000. Same app. Same quality. Different speed. Different income. Claude Code has modes that change how it operates. And shortcuts that cut your workflow time in half. Most people don't know either exists. They use Claude Code in default mode for everything. Like driving a car in first gear on the highway. Technically it works. But everyone is passing you. The video shows you every mode. Every shortcut. Every time-saving trick that separates the people charging $2,000 per project from the people charging $10,000. Speed is money. Literally. Save this post. Follow Himanshu Kumar for the shortcuts that cut my build time by 60%. ↓ 9. Write a Proper Planning Prompt. This is the section that separates amateurs from professionals. And it's the section most people skip. A planning prompt tells Claude Code what you're building before you start building it. Architecture. File structure. Technologies. Features. Constraints. Edge cases. Without a planning prompt, Claude Code guesses. And guessing produces garbage. With a planning prompt, Claude Code executes a clear plan. And clear plans produce working software. The video shows you exactly how to write a planning prompt that makes Claude Code produce professional-grade output on the first try. "But I just want to start coding." That's why your code breaks every time. That's why you restart projects 4 times. That's why nothing you build ever gets finished. Because you refuse to plan. A 5-minute planning prompt saves you 5 hours of debugging. But you'd rather skip the 5 minutes and suffer through the 5 hours because patience isn't your thing. And that's exactly why you're not making money. Planning is the most underpaid skill in coding. And the most overpaid when you master it. Save this post. Follow Himanshu Kumar for the planning prompt templates I use for every client project. ↓ 10. Choose the Right Model. Claude Code lets you select different AI models. Not all models are the same. Not all tasks need the same model. Using the most powerful model for a simple task wastes credits. Using a basic model for a complex task wastes time. The video explains: Which model to use for quick fixes. Which model to use for complex architecture. Which model to use for debugging. Which model to use for code generation. Most people pick one model and use it for everything. That's like using a sledgehammer to hang a picture frame. Model selection is strategy. And strategy is money. The people making $10K/month with Claude Code are strategic about every credit they spend. You're burning through credits because you use the most expensive model to write a hello world. ↓ 11. Use Git and Version Control. If you're not using version control, you're one mistake away from losing everything. Claude Code integrates with Git. Every change tracked. Every version saved. Every mistake reversible. Without Git: Claude makes a change. It breaks something. You can't undo it. You start over. 3 hours wasted. With Git: Claude makes a change. It breaks something. You roll back in 5 seconds. Keep working. Version control isn't optional. It's insurance. And the people not using it are the same people who say "I lost my entire project" like it's something that just happens. It doesn't just happen. It happens because you didn't set up Git. The video walks through the entire Git integration. Save this post. Follow Himanshu Kumar for the Git workflow that's saved every project I've ever built. ↓ 12. Set Up Claude MD and Memory. This is the feature that makes Claude Code feel like a real team member instead of a stranger you explain everything to every time. ClaudeMD is a memory file. You tell Claude Code about your project once. It remembers forever. Coding style preferences. Project architecture decisions. Technology stack. File naming conventions. Business logic rules. Without ClaudeMD: Every new conversation starts from zero. You explain the same things repeatedly. Output is inconsistent. With ClaudeMD: Claude knows your project. Claude follows your rules. Claude produces consistent, professional code. The difference between a sloppy freelancer and a reliable agency is consistency. Claude. MD gives you consistency without the agency overhead. Most people don't set this up and wonder why Claude Code gives different answers every time. ↓ 13. Automate with Tasks. This is where Claude Code stops being a tool and starts being an employee. Tasks let you define repeating workflows. "Every time I push code, run tests." "Every time I create a new file, add boilerplate." "Every time I start a session, check for errors." Automated. Hands-free. Consistent. You're doing these things manually every single day. The same checks. The same steps. The same routine. Tasks do them automatically. So you can focus on the work that actually makes money. Every manual task you automate is time you get back. And time is the only thing you can never make more of. Save this post. Follow Himanshu Kumar for the task automation templates that run my entire workflow. ↓ 14. Explore Features Most People Never Touch. The video covers features that 95% of Claude Code users don't know exist. Because they watched a 3-minute TikTok about Claude Code and think they're experts now. They're not. They're using 5% of a tool that can do everything. The full tutorial goes deep into features that most tutorials skip because they're "too advanced." They're not too advanced. They're too valuable for lazy creators to bother explaining. This video explains all of them. Clearly. For beginners. The 5% of features you don't know about are the 5% that make people rich. ↓ Let's zoom out. I just broke down 14 sections of Claude Code. Setup and installation. Desktop app. Dependencies. Code editor integration. Basic usage. Commands. Modes and shortcuts. Planning prompts. Model selection. Git and version control. Memory and Claude. MD. Tasks and automation. Advanced features. All in one video. All free. All beginner friendly. The person who masters even half of these in the next 2 weeks will be in the top 1% of Claude Code users. The top 1% of Claude Code users are the ones charging $5,000-$10,000 per project and building them in a single afternoon. Everyone else is asking ChatGPT to fix their resume. Same tools. Same access. Completely different outcomes. Because one person treats AI like a toy. And the other treats it like a business. ↓ Here's the hard truth nobody wants to hear. You don't have a talent problem. You don't have an intelligence problem. You don't have a resources problem. You have an action problem. Everything I just listed has a free tutorial right here in the attached video. 33 minutes. That's it. 33 minutes to learn the tool that people are using to build $5,000-$20,000/month businesses. You spent more time today scrolling Twitter than it takes to watch this video. You spent more time this week watching Netflix than it takes to master Claude Code basics. You spent more time this month doing nothing than it would take to completely change your income. The information is free. The tool is accessible. The opportunity is here. The only thing missing is you caring enough to start. ↓ CANCEL your plans this week. This isn't optional anymore. The people learning Claude Code right now will be building apps for the people who didn't learn it. That's not a prediction. That's already happening. Companies are replacing $150/hour developers with one person and Claude Code. If you code: learn Claude Code or become half as valuable by next year. If you don't code: learn Claude Code or miss the biggest opportunity to start earning from tech without a CS degree. There's no path forward that doesn't include AI coding tools. None. You have one window. Right now. This week. ↓ Here's your action plan for the next 7 days: Day 1: Watch the full video. Install Claude Code. Set up dependencies. Day 2: Learn basic usage. Try 5 different commands. Day 3: Write your first planning prompt. Build a small project. Day 4: Set up Claude. MD. Configure your memory file. Day 5: Master modes and shortcuts. Build a second project faster. Day 6: Set up Git integration. Automate with tasks. Day 7: Build something real. A tool, an app, a website. Ship it. 7 days. One tool. One completely different skill set. One completely different income potential. Or 7 more days of scrolling Twitter watching other people build things while you "plan to start." Your call. ↓ This is the most important video you'll watch this year. 33 minutes. Complete Claude Code mastery. From zero to building real projects. Save this post. Come back to it every single day this week. Check off each section as you complete it. Follow Himanshu Kumarfor daily Claude Code breakdowns, advanced tutorials, and the exact workflows that are turning beginners into $10K/month builders. The only thing between you and $10K/month with Claude Code is this video and 7 days. Don't waste them. You Must Follow me Himanshu Kumar, so i can send you DM.

Himanshu Kumar

85,668 görüntüleme • 3 ay önce

It’s taken nearly a full year of my life - First $LMND, soon everything else. I’ve finally launched IronicApe - not another data provider but what will become (overtime) the world’s leading digital analyst, 100x cheaper and 100x faster. I built it around a simple belief: data is only useful when you understand the context, the source, the business and why the number matters. It brings together narrated earnings updates, company “stories”, operating performance, ownership, fundamentals, market sentiment, technical analysis, valuation, SEC filings, source checks, point-in-time backtesting, community research and Cortex - our map of the drivers and dependencies behind a business… a business is not GAAP accounting, everything connects to everything else and every reaction has an equal and opposite reaction. The walk-forward Machine learning model moves through history one reporting period at a time, using only information available at that point (blind) - It forecasts, compares the result with what actually happened and learns which signals deserve more weight - without quietly learning from the future. It tests possible causal relationships; it doesn’t pretend correlation is proof. I’ve tried my best to make everything understandable for retail investors while retaining enough technical depth, granular analysis and transparent evidence to be useful to leading analysts, all financial data is deterministically retrieved and source backed. Portfolio management (that’s actually useful), a company screener and a much more comprehensive Learning Academy are coming soon… IronicApe is meant for all investors no matter their age, background, education or experience - longer term it will help take a first time investor from understanding the terminology most with years of experience just know, what is revenue or gross margin all the way to complex MBA level knowledge and beyond. For now, please go forth and try it. Find every bug, missing feature, confusing explanation, bad assumption and change you think it needs. Honest feedback is very welcome! If you read this far, fair play! There’s also 10 hidden Paper Bag Investor hidden around the app. I had Ai place them, even I don’t know where they all are, I’ve only managed to find 5 so far! 😅 Together, we can overtime level the playing field with Wall street and democratise financial analysis. I turned down a 7 figure investment to build this for the retail community. It’s not perfect, nothing is - but my commitment to you all is to never stop pushing the boundary of what’s possible.. to iterative, innovate and strive to win together!! And while it’s not perfect, I can tell you this for free… it’s a fu*k load better than Book value per share!!! 🍋 It has real cost to maintain - I’m not yet eligible to monetise from X and I really DON’T want to charge for this. So if you find value in it, please like, share and follow. I also appreciate I post a lot of stuff that people may not want to follow to get access, so I’ll be adding a non follower paid subscription and free ad’s plan soon. For now, when you link your X account it checks follower status to unlock content, it uses the least access x provides to check follower status - I don’t even get your email. Apes Stronger Together!

Ironic Ape

29,409 görüntüleme • 14 gün önce

HERMES AGENT SUPPORTS 300+ MODELS. PICKING THE RIGHT ONE PER TASK IS THE DIFFERENCE BETWEEN $5/MONTH AND $50. STARTING OUT: Claude Sonnet 4.6. official recommendation from Nous Research. "the model this project was built and tested with." strong reasoning. reliable tool calling. mid-range pricing. PREMIUM TIER: Claude Opus 4.8. best coding benchmarks available. self-correcting reasoning. catches its own mistakes. 1M context. use for demanding tasks where quality matters. GPT-5.5. #1 Chatbot Arena. #1 GPQA Diamond reasoning (94.1%). #1 creative writing. 2M context. handles entire codebases in one pass. Grok 4.30. the only frontier model with live X firehose access. real-time social data, breaking news, market sentiment. connects via Grok OAuth. no separate API key. Grok-Composer-2.5-Fast (v0.17.0). Cursor's coding model. 200K context. available through your Grok subscription via OAuth. no extra cost if you already pay for Grok. MID-RANGE TIER: Claude Sonnet 4.6. best balance of quality and cost for daily use. strongest prose and tool calling in this tier. Gemini 2.5 Pro. Google Search grounding built in. cites sources. verifies claims. pulls current data. 2M context. best for research-heavy workflows. GPT-4.1. reliable tool calling. solid general reasoning. good middle ground when you need OpenAI compatibility. BUDGET TIER: Claude Haiku 4.5. fastest Anthropic model. cheapest paid Claude option. strong at classification, routing, simple queries. use for auxiliary tasks: compression, vision, web extraction, approval scoring. DeepSeek V4. best cost-to-quality ratio in the market. 90% cache discount on repeated context. use for sub-agents and bulk parallel work. DeepSeek V4 Flash. cheapest paid model worth using. 1M context. MIT license. self-hostable. use for cron jobs, monitoring, routine searches. MiniMax M3. Nous Research and MiniMax collaborating on optimization. 1M context via lightning attention. 59% SWE-Bench Pro. beats several premium models on coding. one of the most-used models inside Hermes. FREE / LOCAL: Qwen 3.5 27B via Ollama. 16GB VRAM. reliable tool calling. best free local model for Hermes as of mid-2026. Qwen 3 8B. 8GB VRAM. fits a $7 VPS. handles routine tasks at zero API cost. Llama 4 Maverick. best open-weight tool calling. 1M context. needs more VRAM but strongest local option. HOW TO ASSIGN MODELS: main model: Desktop app / Dashboard → Models → switch sub-agent model: set in Desktop app, Dashboard, or config.yaml: delegation: model: "deepseek/deepseek-v4" auxiliary models (compression, vision, web extract): Desktop app / Dashboard → Models → Auxiliary Haiku 4.5 or Gemini Flash work well here. saves significantly when your main model is premium. per-profile: each Hermes profile gets its own model. Scout on DeepSeek. Analyst on Sonnet. Briefer on budget model. Coder on Opus. per-cron-job: pin a specific model to any cron job. morning brief on Haiku. deep research on Sonnet. monitoring on DeepSeek Flash. each job uses only the model it needs. per-session: /model deepseek/deepseek-v4-flash hot-swap mid-conversation. no restart needed. FALLBACK CHAINS: if your primary model is unavailable, Hermes automatically switches to the next provider. rate limit or server error = next model in the chain. no failed runs. no manual intervention. set in Desktop app, Dashboard, or config.yaml: fallback_providers: - openrouter - nous - codex PROVIDER PATHS: OPENROUTER: 300+ models under one API key. pay per token. most flexible. NOUS PORTAL: 300+ models + Tool Gateway (web search, image gen, TTS, browser). one OAuth. one subscription. 10% off token-billed providers. CHATGPT SUB: GPT-5.5 + Grok via OAuth. included tokens with $20 subscription. OLLAMA: free. local. private. zero API cost. your hardware only. mix providers across profiles and tasks. Scout on OpenRouter. Analyst on Nous Portal. Coder on ChatGPT sub. Monitor on Ollama. THE RULE: premium for work that needs deep reasoning. mid-range for daily driver tasks. budget for volume and background work. free for monitoring and routine jobs. pricing changes fast. check openrouter ai for current rates before committing. Which is your favourite model and for what task? full 15 levels breakdown in the article 👇

YanXbt

17,138 görüntüleme • 2 ay önce