Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Automation tools can encode steps. They can't encode judgment. “Watch 3 competitors' prices, ping me on a 5% drop.” The n8n version needed: - a URL - a CSS selector - a sheet ID …then broke the same evening when my target site's HTML didn't match the template author's....

13,758 Aufrufe • vor 1 Monat •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

i watched gemma 4 12b build something genuinely impressive today, and then loop itself to death right in front of me. the full run is in the video, sped up but completely uncut, watch it to the end and you will catch the exact moment it stops building and starts looping right in the middle of the work. the task was clean, build a single file gravity simulator, n-body physics, orbits, collisions, running locally on one 3090 through an agent. and for ten minutes it was a joy to watch. it reached for a symplectic integrator on its own, the correct one, the kind that keeps orbits stable instead of spiralling out. real gravity with softening, proper orbital velocities, momentum conserved on collision. the physics was right. the thing actually worked. then on the very last step, writing a few tests to prove its own code, it fell into a loop. not a crash, a loop. it started repeating itself and would not stop. ten more minutes, thirty four thousand tokens into a single answer, the same fragments over and over, until i killed it myself. so it's not that gemma can't code. it did the hard part beautifully. it cannot finish. it cannot hold a long task together without unravelling, and finishing is the entire job in agentic work. here's the part that stings. i run this exact task, same harness, same card, on the chinese open models, qwen especially, and i never see this. they build it, they test it, they stop. every single time. google has the raw capability, you can see it sitting right there in the code, and then the model loops itself to death on a task a 27b from alibaba finishes clean. open weights, apache 2.0, so much to love on paper. i just need it to know when to stop talking.

Sudo su

39,719 Aufrufe • vor 2 Monaten

BlackRock runs on 20,000 people. Elon's Grok Bot runs the same shape for $300 a month, and it hires its own staff. You do not get an assistant. You get a company that hires. It does not throw ten agents at your problem and hand you the pile. It makes one agent that makes 10, and those ten make a 100. > LAYER ONE is one agent, the chief of staff, and it never touches the market > LAYER TWO is six desk heads, one job each, every one on its own computer with its own logins > LAYER THREE is whatever those six decide they need, spun up on the spot and shut down when the work is done Nobody writes a task list. You hand out job titles and the org fills itself in underneath. The swarm is never the same twice. Agents get spun up for one job, finish it, and are gone before I ever read their names. Not one of them sees the whole picture. The answer only exists after they hand off to each other. Wall Street cannot copy that. You cannot hire a hundred people for eleven minutes. BlackRock holds that shape together with a risk system called Aladdin. Mine holds it together with one agent that is only allowed to say no. I gave it $1,000 and told it to grow the money or get deleted. 15 hours later it was holding $3,900, on an address anyone can open and read. I was asleep for most of it, and I have still not written a line of code. The whole thing runs with my laptop shut, because none of it lives on my laptop. Setup is one evening. Create the chief, hand out the titles, run one trade on your screen while they watch, connect Telegram. Ten years ago a machine this shape had its name on a tower. Mine has a name I typed into a box. Save this while the whole thing still fits on one screen.

cvxv666

33,932 Aufrufe • vor 2 Tagen

#1 skill for developers in 2026: Automate everything you can using AI. I bet my lunch your team is dealing with all of these: • Stale documentation • Outdated dependencies • Poor test coverage • Deprecated APIs Every company I work with has these same problems. You can solve all of these right now. Automatically. Using AI. Here are 3 examples. Watch the attached video: I'm using Ona Automations to tackle this. These are background agents that run in the cloud, in a fully configured dev environment with your toolchain, your dependencies, and your services. You can run an unlimited number of these agents in parallel and across all your repositories. Claude Code and Codex only run locally, so they are hard to scale, and you can't run them when your computer is closed. Ona runs in the cloud. Here are the three examples: 1. Test coverage Run a nightly automation to identify any untested code paths, generate candidate tests, verify they pass, and open draft PRs. You wake up every morning to PRs that improve your test coverage. 2. Dependency upgrades Configure a weekly automation that bumps a dependency version, runs your full test suite, and reports any regressions. If everything is clean, it opens a PR. If something breaks, it opens a report so you can decide what to do. 3. Documentation auditing Set up a weekly automation that checks recent commits against your README file and setup guides, identifies broken examples and outdated instructions, and opens a PR with fixes.

Santiago

25,804 Aufrufe • vor 6 Monaten

I charge $999 to ask a business owner questions for 45 minutes. Then Claude does the analysis in 5 minutes. I call it the AI Tools Assessment. It finds 3 to 7 off-the-shelf tools that reclaim 5 to 10 hours a week, and it's the front door to upsells from $3,500 projects to $2,000/month retainers. Here's the entire model: 1) The discovery call is questions only. "Walk me through yesterday." "What tasks do you dread?" "Where does work pile up?" No pitching. A free AI notetaker captures the transcript. 2) Claude runs the entire analysis. Paste the transcript, run one skill, and it pulls the pain points and prescribes the tools in about 5 minutes. It catches patterns you missed on the call. 3) When Claude whiffs on a tool, and fill the gaps. Thousands of tools, grouped by industry. 4) The report is 9 slides. Executive summary, effort vs impact matrix, tool recommendations, a 4-day quick win plan, and the financial impact. I open sourced the template free at 5) I go for the close on the review call. Three questions: which of these is most urgent, do you want to DIY or get help, and what's your timeline? 50 to 60% of clients ask you to implement it for them. 6) Process redesign sells for $3,500 with zero automation. One e-commerce client had an 18-step ad workflow. We cut it to 9 steps. Fixed the process, didn't touch AI, charged $3,500. 7) Knowledge systems are $3K builds. A business broker got 400 emails per listing. We trained a custom GPT on the marketing package, and buyers called it the best broker experience they've had. 8) You don't need an audience to sell this. One guy walked into 30 local businesses offering a free 15-minute mini assessment. 5 meetings, 2 clients. The free mini assessment is the hook for every channel. 9) Co-working spaces are the cheat code. Dennis in our community hosted his first free AI office hours this week. 9 people showed up, 2 became warm leads. 10) AI Concierge is the best upsell of all. Two 45-minute calls a month at $1,200 to $2,000. I have 5 clients and my blended rate is about $1,100 an hour at 99.9% net margin. Two things that make this work: 1) Sell the diagnosis before the cure. The $999 assessment is a paid discovery call that qualifies the buyer and tees up every upsell on the menu. 2) High perceived value can cost you nothing. Unlimited Voxer access sells the retainer. In 3 months across 5 clients I've gotten 4 messages. Full breakdown below. watch, implement, make money. (also available on the Build With AI podcast wherever you get your pods)

Corey Ganim

49,064 Aufrufe • vor 1 Monat