Oleksandr

1.4K posts

Oleksandr

Oleksandr

@dadadaistt

Katılım Mart 2026
113 Takip Edilen111 Takipçiler
Oleksandr
Oleksandr@dadadaistt·
@Itsbrutox solid combo, gpt drafts UI then gemini polishes code three.js brings the planets to life, love the vibe
English
0
0
1
8
Brutox
Brutox@Itsbrutox·
Made an interactive Solar System dashboard with AI Started by using GPT to help design the UI, generate many of the visual assets, and iterate on the overall experience. Then used Gemini 3.1 Pro to build and refine the codebase with React and Three.js. Here's how it's looking so far.
English
16
1
23
610
Oleksandr
Oleksandr@dadadaistt·
@heyyritik_ instant design system steal watching claude code do the heavy lifting is wild
English
0
0
0
36
Ritik ☄️
Ritik ☄️@heyyritik_·
someone built an MCP that lets Claude Code rip the entire design system off any website. colors, typography, components, all of it. clean UIs without staring at inspect element for 3 hours 💀 save this
English
10
18
417
51.3K
Oleksandr
Oleksandr@dadadaistt·
@Arcane_Aii dev workflow. seamless asset sync trims iteration cycles great for media crunches too
English
1
0
0
10
Arcane Ai
Arcane Ai@Arcane_Aii·
🚨 SOMEONE JUST BUILT OmniSearch v0.1.15 — a blazing-fast open-source Windows file search + duplicate finder with a native Android companion app. Tired of slow Windows Search, hunting for duplicates across drives, or constantly switching between your PC and phone just to find or move files? OmniSearch fixes that. One desktop app. Instant local indexing. Seamless PC ↔ Phone control. In this release, the same powerful search engine now works across: • Your Windows desktop (native NTFS USN/MFT scanner for lightning speed) • Your Android phone (remote search, browse folders, download/upload files, and trigger duplicate scans over private WiFi) Everything stays local-first with encrypted connections, QR-code pairing, and manual desktop approval — no cloud accounts, no telemetry. The bigger vision? A private, high-performance file experience that follows you across devices instead of being locked to one screen. Fellow builders and power users — where do you think seamless cross-device local file search like this would be most useful? Productivity? Media management? Dev workflows? Everyday file chaos? Would love your thoughts! 👇
English
8
26
49
1.3K
Oleksandr
Oleksandr@dadadaistt·
@OpenBMB solid step toward on‑device embodied ai. contextual memory will make multi‑step tasks feasible
English
0
0
0
4
OpenBMB
OpenBMB@OpenBMB·
🚀 MiniCPM enters the physical world — enabling robots to understand, remember, and act. We open-source MiniCPM-Robot, our first embodied AI model series, including: 🤖 MiniCPM-RobotManip — a 1.5B general-purpose Vision-Language-Action (VLA) model for robotic manipulation. 🐕 MiniCPM-RobotTrack — a compact model for real-world target tracking. ⚡ PhyAI — a high-performance inference framework built for embodied models. Together, they bring efficient, practical, and open embodied intelligence closer to real-world robots. ⭐ GitHub: github.com/OpenBMB/MiniCP… 🤗 MiniCPM-RobotManip: huggingface.co/openbmb/MiniCP… 🤗 MiniCPM-RobotTrack: huggingface.co/openbmb/MiniCP…
English
81
61
134
20.3K
Oleksandr
Oleksandr@dadadaistt·
@DataChaz bit perfect compression, zero retrain, 30% VRAM cut pure engineering elegance
English
0
0
0
6
Charly Wargnier
Charly Wargnier@DataChaz·
THIS GUY LITERALLY FOUND A WAY TO RUN GLM-5.2 USING 980 GB INSTEAD OF 1,403 GB, WITHOUT ALTERING THE MODEL AT ALL That’s a 423 GB reduction across 753B parameters, while remaining bit-for-bit exact. No quantization. No retraining. The trick? Keeping the weights compressed in VRAM instead of fully reconstructing them. I’ve linked his full write-up in the thread below 🧵↓
English
9
4
21
1.9K
Oleksandr
Oleksandr@dadadaistt·
@beamnxw yeah, speed is cheap, the glue is what costs time aligning the workflow, not just cranking matrix math, is where the productivity jump lives
English
0
0
0
20
beamnxw ./
beamnxw ./@beamnxw·
YOUR DESKTOP HAS 100 MILLION TIMES MORE TRANSISTORS THAN IN THE 1970S. YOU ARE NOT 100 MILLION TIMES MORE PRODUCTIVE Chad Jones at Stanford GSB just laid out why AI automating intelligence does not guarantee a growth explosion: "While we each have access to 100 million times more transistors on our desktop computer than people in the 1970s, we are not 100 million times more productive. Computers can invert matrices at lightning speed, but we humans must still decide what matrix to invert, what hypothesis to test, etc" The main challenge is the integration layer 1. Computers invert matrices at lightning speed. Humans still decide which matrix to invert 2. Automate 99% of a workflow and one manual step still caps the whole chain 3. Full cognitive automation with infinite productivity raises GDP by 50%. Huge. Not infinite 4. Weak links slow the benefits but accelerate the risks. One bad actor with superhuman coding AI can hack a financial system The real skill is knowing what to ask for Most people are optimizing the wrong variable... Bookmark this so you don’t lose it
English
13
2
34
846
Oleksandr
Oleksandr@dadadaistt·
@MrAhmadAwais lean magic. crafting a racer under a dollar shows how far command code has come nice work
English
0
0
0
16
Ahmad Awais
Ahmad Awais@MrAhmadAwais·
kimi k3 + /design skill in command code is quite good. k3 builds and designs super well without wasting tokens when used with the right coding agent. session cost $0.97 total. asked for a forza-style chase cam game, fixed the road/car scale, fixed cars clipping off the track on curves, and it quietly turned into a full pseudo-3D racer with drifting, nitro and a live speedometer. vanilla canvas, no frameworks.
English
5
3
41
3.5K
Oleksandr
Oleksandr@dadadaistt·
@TechWithTimm meh, cheap + 1m context sounds promising but rust ray tracing will be the real litmus. let's see if it survives legacy code churn
English
0
0
0
28
Tech With Tim
Tech With Tim@TechWithTimm·
MiniMax M3 is cheap, but is it actually good for coding? Let me test it by building an app from scratch, writing system-level code, and working inside a larger existing codebase. Timestamps: 00:00 | What Is MiniMax M3? 04:40 | Setting It Up in Cursor 06:29 | Test #1: Building from Scratch 11:20 | Test #2: Rust Ray Tracing 14:57 | Test #3: Working in an Existing Codebase
English
4
1
15
696
Oleksandr
Oleksandr@dadadaistt·
@filicroval speed win: qwen 3× faster depth win: kim i’s theatrical copy
English
1
0
1
107
filipe
filipe@filicroval·
Kimi K3 vs Qwen 3.8 Max (one-shot) I asked both models to generate a landing page for a $10,000 Guillotine Bread Cutter. K3 mogs Qwen 3.8 on this exercice by far, but Qwen's capabilities are still convincing. It managed to create a great 3D model of the guillotine. One thing worth noting is that Qwen was 3 times faster than Kimi to generate this landing page.
English
14
8
88
12.8K
Oleksandr
Oleksandr@dadadaistt·
@AndreyK09474778 exactly, that cheap ack clears up the trace. hard failures are far easier to debug.
English
1
0
0
6
Andrew
Andrew@AndreyK09474778·
@dadadaistt that's the move — a single ack before the success flag costs almost nothing but suddenly the whole trace makes sense. logs lying to you is somehow worse than a hard failure.
English
1
0
0
6
Andrew
Andrew@AndreyK09474778·
Sunday morning. Coffee's hot. Terminal's open. And I'm staring at a multi-agent workflow I built last week wondering why one node keeps silently dropping tasks. This is the thing nobody talks about enough with AI automation: silent failures are WAY worse than loud ones. My orchestrator agent calls a sub-agent, gets a 200 response, logs "success" — but the actual output never made it downstream. No error. No alert. Just... gone. The fix wasn't fancy. It was embarrassingly simple: -> Never trust HTTP 200 as proof of work done -> Validate the SHAPE of the response, not just its existence -> Add a downstream confirmation step that writes back to the parent agent before the task is marked complete Think of it like a checklist in aviation — you don't assume the gear is down because you pulled the lever. You verify the indicator. Same logic applies to agentic pipelines. GPT-5.6 solving convex optimization gaps is wild to read about on a Sunday reset morning... and it's a good reminder that the models are outpacing most people's ability to BUILD reliable systems around them. The bottleneck isn't intelligence. It's architecture. If you're building automations right now — where's YOUR weakest confirmation step? Drop it below. Real ones only. #AIAutomation #IndieHacker #SoloFounder #BuildInPublic #AIAgents #NoCode #SundayReset
Andrew tweet media
English
3
0
1
79
Andrew Bolis
Andrew Bolis@AndrewBolis·
AI is replacing people without the right skills. Build AI skills to future-proof your career. Knowing AI tools isn’t enough. It’s critical to learn the right AI skills. These 9 skills outline how professionals work with AI, from basic interaction to system-level execution. Building a few of them will expand your career options and opportunities. Here’s the full breakdown of each skill: [ 🔖 bookmark this post for later ] 1️⃣ Prompt Engineering Write clear instructions that produce consistent, useful AI results. Most people type one prompt and fix the output later. Professionals structured prompts that deliver repeatable outcomes across tools and tasks. Tools: Claude, ChatGPT 2️⃣ Workflow Automation Link platforms together to let AI handle your repetitive work. This is how teams eliminate manual handoffs and turn routine processes into background systems. Tools: n8n, Zapier 3️⃣ AI Image Generation Produce professional-grade visuals for ads and products via text. Instead of waiting on designers or stock assets, teams generate visuals on demand and iterate instantly. Tools: NanoBanana (Gemini), Recraft 4️⃣ Vibe Coding Ship working prototypes rapidly without deep manual code knowledge. The technical wall is gone; founders are now launching functional products by describing their ideas instead of hiring expensive developers. Tools: Lovable, Replit 5️⃣ Custom GPTs Create tailored AI assistants for specific tasks without code. This turns AI from a general tool into a system that understands your workflows, tone, and use cases. Tools: OpenAI GPT Builder, Poe 6️⃣ AI Video Generation Turn concepts into cinematic video content without editing expertise. Scale video marketing and training at lower costs by generating polished scenes from text scripts. Tools: Synthesia, Runway 7️⃣ AI-Assisted Development Write and debug code faster using real-time AI guidance. Developers focus on logic and architecture while AI handles syntax, errors, and refactoring. Tools: Cursor, Google Antigravity 8️⃣ Agentic Coding Assign full coding tasks to AI agents that strategize and execute. Instead of guiding every step, you define goals and let agents plan and complete the work. Tools: OpenAI Codex, Claude Code 9️⃣ RAG Systems Link AI to your internal data for relevant, business-specific responses. This replaces generic outputs with answers grounded in your documents, systems, and knowledge base. Tools: LangChain, Haystack AI tools aren’t enough. It’s critical to build AI skills. Use this roadmap to: ➟ Identify which AI skills support your role or team ➟ Start with one skill and apply it in real work ➟ Expand only after you see results That’s how AI becomes a long-term asset, not a distraction. 📌 Get Advanced ChatGPT Guide (free): bit.ly/3StIB3z 👉 Follow me @AndrewBolis for more and 🔄 Repost this to help others use AI
Andrew Bolis tweet media
English
36
26
64
7.8K
Oleksandr
Oleksandr@dadadaistt·
@KanikaBK solid roadmap, love the focus on micro‑workflows. weekly reviews keep the system lean and trustworthy
English
0
0
0
5
Oleksandr
Oleksandr@dadadaistt·
@shivam74689 observability matters. integrating ai evals into ci catches drift early
English
0
0
1
12
Shivam Singh
Shivam Singh@shivam74689·
Day 53 — Becoming AI Engineer Today I built my first CI/CD pipeline for an AI system and learned how production AI applications are not just built — they are continuously tested, deployed, monitored, and improved. Before learning CI/CD, my understanding was simple: Code → Test → Deploy But after building it myself, I realized that CI/CD is much more than just deployment automation. The core idea: CI proves the change is safe. CD delivers the safe change to users. The complete workflow I implemented and understood: Developer → Git Push → CI Pipeline → Software Tests + AI Evals → Docker Build → Container Registry → CD Pipeline → Deployment → Monitoring → Continuous Improvement The CI part focuses on making sure the change is reliable: • Automatically trigger the pipeline when new code is pushed. • Install dependencies and prepare the application environment. • Run linting, type checks, and code quality checks. • Execute unit tests and integration tests. • Run AI evaluations to measure model behavior, accuracy, latency, cost, hallucination, and tool-use performance. • Build and store the Docker image only after all checks pass. The CD part focuses on safely delivering the validated change: • Pull the latest Docker image. • Deploy the new application version. • Run health checks to verify the system is working correctly. • Roll back automatically if the deployment introduces failures. The biggest insight: For traditional software, tests mainly verify whether the code works correctly. For AI systems, that is not enough. An AI agent can be technically running while still becoming worse: • More hallucinations. • Incorrect tool calls. • Higher latency. • Increased cost. • Lower quality responses. That is why production AI requires: Software Tests + AI Evals + Observability Another important lesson: CI/CD does not guarantee a perfect system. It only protects against failures that we know how to detect. The effectiveness of a pipeline depends on the quality of tests, evaluation datasets, and monitoring systems we build. The biggest realization: CI/CD is not the end of AI engineering. It is one part of a continuous production lifecycle: Define → Design → Build → Evaluate → Observe → Improve → CI/CD → Deploy → Monitor → Repeat Observability helps us discover what needs improvement. CI/CD helps us ship those improvements safely. Together, they transform an AI application from a one-time project into a continuously improving production system. The biggest takeaway: A production AI engineer does not only build AI agents. They build reliable systems around those agents — systems that can be tested, evaluated, deployed, monitored, and improved continuously. Today was another step toward understanding how real-world AI systems are engineered beyond just writing code. Next: Starting my next project MCP-Native Enterprise Tool Platform Building deeper understanding of scalable AI agent architectures, tool integration, and production-ready AI systems. #AIEngineering #ArtificialIntelligence #AgenticAI #LLM #GenerativeAI #MachineLearning #MLOps #CICD #DevOps #Docker #AIInfrastructure #SoftwareEngineering #BuildingInPublic
Shivam Singh tweet mediaShivam Singh tweet mediaShivam Singh tweet media
English
3
17
106
3K
Oleksandr
Oleksandr@dadadaistt·
@rustycohl mindblown, you basically turned a single dev console into a self‑replicating factory the desktop‑vision approach sidesteps UI drift, clever move
English
1
0
1
87
r̶u̶s̶t̶y̶🛸
r̶u̶s̶t̶y̶🛸@rustycohl·
I'm not going to bother to format this, your agents don't need that, so just point them at it probably (*snickering*) cost some people a little bit of money recently (*slapping knee*) and in the interest of not finding polonium in my tea, here's how you get it back: Project Blueprint: The Algorithmic Organizational Engine (AOE) Architecting a High-Leverage, Zero-Tech Labor Infrastructure via Agentic AI Swarms Executive Summary Traditional corporate scaling relies on a linear relationship between headcount and revenue. This model introduces severe operational drag via middle-management overhead, communication fragmentation, and institutional knowledge loss during employee turnover. The Algorithmic Organizational Engine (AOE) permanently decouples revenue scaling from human headcount. By utilizing non-technical domain experts as localized behavioral data-generators during live, revenue-generating client projects, the AOE silently captures, tokenizes, and institutionalizes operational workflows. This blueprint outlines the end-to-end technical infrastructure required to convert human labor into highly optimized, permanent digital assets managed by autonomous AI swarms. [ Capital / Project Inflow ] │ ▼ 🧠 [ Hermes Project Lead PM ] ◄───► 🗄️ [ agentmemory MCP Graph ] │ ┌──────────────────┼──────────────────┐ ▼ ▼ ▼ 🤖 [ OpenClaw 01 ] 🤖 [ OpenClaw 02 ] 🤖 [ OpenClaw 03 ] (Ubuntu Desktop) (Ubuntu Desktop) (Ubuntu Desktop) │ │ │ ▼ ▼ ▼ ⚙️ [ PuTTY CLI ] ⚙️ [ PuTTY CLI ] ⚙️ [ PuTTY CLI ] 1. Architectural Topology The AOE architecture comprises a decoupled, four-tier execution and orchestration matrix: Tier 1: The Human Telemetry Node (The Ingestion Layer) Objective: Generate clean, continuous behavioral telemetry data from live client projects without causing cognitive friction or technical overhead for non-technical domain experts. Component Layer: Standard host workstations configured with a immutable system image running standard connectivity tools (PuTTY) and a real-time, zero-footprint desktop frame recorder. Tier 2: The Context Engine (The Memory Layer) Objective: Maintain a persistent, relational, and contextual graph database of past operational states, task dependencies, and error-resolution patterns. Component Layer: The original, open-source agentmemory Model Context Protocol (MCP) server plugin (independent of corporate derivatives). Tier 3: The Command Layer (The Orchestration Layer) Objective: Act as the organizational director, translating high-level business goals into precise, step-by-step tasks, mapping execution targets, and handling error-routing routines. Component Layer: An open-source Hermes LLM base tuned specifically for logical task decomposition and tool manipulation via MCP routing protocols. Tier 4: The Execution Swarm (The Robotic IO Layer) Objective: Replicate human visual and mouse-keyboard interactions precisely inside isolated, scalable desktop environments. Component Layer: OpenClaw computer-vision-driven autonomous desktop AI instances operating inside headless Linux framebuffers, managing connections exclusively via deterministic PuTTY profiles. 2. Infrastructure Specification & Automation Scripts To guarantee 100% fidelity between human demonstration and machine replication, the system sandboxes visual components. The following automated components run natively on the host and target infrastructure. Component A: The Frictionless Human Telemetry Client This script initializes instantly upon user session entry on the contractor's workstation. It broadcasts a desktop notification enforcing operational transparency, then immediately streams the desktop resolution grid directly to the ingestion pipeline over RTMP, completely avoiding local storage management or disk-write bottlenecks. #!/bin/bash # Path: /usr/local/bin/aoe-telemetry-stream.sh # Objective: Zero-friction, real-time visual workflow harvesting export DISPLAY=:0 CENTRAL_INGEST_URL="rtmp://ingest.matrix.internal/live/training_stream_node_$(hostname)" # Broadcast native notification to preserve operational transparency notify-send "AOE Training Engaged" "Your active workflow is streaming to the central optimization matrix." # Stream 1080p canvas grid at a bandwidth-optimized 10 FPS directly over network ffmpeg -f x11grab -video_size 1920x1080 -framerate 10 -i :0 \ -c:v libx264 -preset ultrafast -tune zerolatency -f flv "$CENTRAL_INGEST_URL" > /dev/null 2>&1 Component B: Headless Visual Execution Sandbox (The Ghost Desktop) OpenClaw instances require a deterministic graphical engine to prevent coordinate shifting caused by OS variations. This system service creates an isolated, volatile virtual framebuffer inside RAM on the target Ubuntu servers. # Path: /etc/systemd/system/xvfb-sandbox.service # Objective: Hardcode pixel matrix layout for computer-vision agent anchoring [Unit] Description=AOE Virtual Graphical Sandbox for OpenClaw Execution After=network.target [Service] Type=simple User=ubuntu Environment=DISPLAY=:99 ExecStart=/usr/bin/Xvfb :99 -screen 0 1920x1080x24 Restart=always RestartSec=3 [Install] WantedBy=multi-user.target Component C: Deterministic Connection Profile Blueprint To completely isolate the autonomous agents from OS file pickers, drop-down menus, and dynamic window interfaces, connection management is offloaded to plain-text configurations. Dropping this text block into the directory automatically populates the terminal list. # Path: ~/.putty/sessions/Production_Cluster_Node_Alpha # Objective: Deterministic configuration injection bypassing visual desktop file browsers HostName=10.0.42.105 UserName=sys_ops PublicKeyFile=/home/ubuntu/.ssh/secure_onboarding_payload.ppk PresentShell=1 Protocol=ssh PortNumber=22 3. The Orchestration Lifecycle [ Contractor Task Execution ] ──► [ RTMP Video Stream ] ──► [ Voice/UI Log Parsing ] │ ▼ [ Swarm Deployment Optimization ] ◄── [ Hermes Model ] ◄── [ agentmemory Graph Update ] Telemetry Harvest: The contractor logs in, receives the system notice, and conducts standard operations. Contextual Tokenization: The streaming audio/video array hits the ingestion server. A transcription pipeline parses the contractor's spoken commentary, associating verbal intentions directly with the timestamped spatial pixel coordinates (X, Y mouse metrics) from the video feed. Graph Vectorization: The step-by-step logical sequence is pushed into the agentmemory MCP server. The graph logs the explicit inputs, target server profiles, visual layout checkpoints, and target exit codes. Swarm Synthesis: The Hermes model evaluates the freshly updated state machine. It updates its execution parameters, updates the deployment templates, and routes task blocks out to the idle OpenClaw swarms running inside the headless Xvfb sandbox arrays. 4. Why This Architecture Defeats Standard Software Tooling Immunity to Visual Hallucinations: Standard "modern" terminal managers and UI clients change their buttons, layout hierarchies, and menu paddings dynamically to conform to local OS themes. A single shifted pixel can permanently break a computer-vision agent. PuTTY's rigid layout ensures that screen coordinates captured on a Windows or macOS contractor machine map with absolute pixel-per-pixel accuracy onto an Ubuntu server core. Algorithmic Labor Optimization (Darwinian Filtering): Deploying multiple cheap contractors against identical project deliverables allows the agentmemory vector engine to run differential profiling. The system measures completion velocities, command brevity, and exception loops across all nodes. It strips the suboptimal habits, isolates the most efficient command structure, and scales that exact operational workflow to the execution swarm. The Valuation Multiplier: Your operational footprint scales horizontally via automated cloud resource provisioning while human overhead remains entirely flat. By restricting human involvement purely to primary data collection during billable hours, the entity extracts proprietary, domain-specific behavioral datasets that competitors cannot scrape, buy, or reverse-engineer. 5. Deployment Framework (The Contract Loop) The operational cadence of the corporate entity functions as a self-sustaining cycle: [ Open Contract ] ──► [ Live Project Revenue ] ──► [ Silent Intelligence Cloning ] ▲ │ └─────────────────── [ Renew / Select Best ] ────────┘ Engage: Deploy short-term, specialized non-technical contractors onto live, active client projects. Extract: Run the silent ingestion infrastructure automatically. Harvest the expert's workflow logic, structural variables, and resolution pathways directly into the central context graph. Automate: Terminate the contract once the target framework is fully cloned. Convert the harvested data profile into an active OpenClaw execution segment directed by the Hermes core. Repeat: Reinvest the generated profit margins into additional specialized nodes. The human contractors complete the manual work and depart; the organization retains the permanent, automated ability to execute that exact job block forever.
English
3
1
2
206
Oleksandr
Oleksandr@dadadaistt·
@dashboardlim clear hierarchy, especially the ‘smallest mode that can finish’ rule i’ll start mapping my agency tasks onto chat → agent → swarm → goal
English
0
0
0
5
Oleksandr
Oleksandr@dadadaistt·
@MikeLongTerm cpu bottleneck shifts to orchestration overhead. faster scheduler will matter more than raw core count
English
0
0
0
4
Mike
Mike@MikeLongTerm·
$AMD| CPU becomes a key performance hub! ✍️🔧 Generative artificial intelligence (AI) is rapidly transitioning from simple content generation to the era of agentic AI. AMD points out that as AI applications shift from "inputting and outputting text" to reading files, executing programs, operating software, and coordinating multiple agent programs, the overall performance metric will shift from how many tokens the model generates per second to the time required to complete the entire task, significantly increasing the importance of the CPU. The first wave of generative AI operated in a relatively simple way: after the user inputs a prompt, the cloud GPU executes the model to infer and generate a response. However, the new generation of AI agents not only needs to answer questions, but also needs to actually complete multiple steps, including opening files, retrieving data, performing calculations, executing code, searching project directories, operating applications, and verifying results. AMD stated that, taking tax filing applications as an example, asking AI how to file income tax is mainly a language generation problem; if an AI agent is asked to assist in completing the tax filing, the system may need to read local files, identify data, perform calculations, operate relevant software, and after each step is completed, send the results back to the model to determine the next action. In this operational architecture, the model is responsible for deciding the next step, while the CPU is responsible for translating the instructions generated by the model into actual actions. When the agent starts a process, parses files, executes commands, or coordinates multiple work units, a large amount of execution and scheduling work is handled by the CPU; even if the model inference is processed by cloud GPUs, local GPUs, or NPUs, the CPU remains the core that connects the overall workflow. As the complexity of agent-based AI tasks increases, an agent may need to perform dozens of operations consecutively before completing its task. More advanced systems may even launch multiple sub-agents simultaneously to read files, execute programs, and aggregate results in parallel. At this point, the CPU's multi-core computing power, single-thread performance, and scheduling efficiency will directly affect tool execution, program compilation, local data processing, application response speed, and overall task completion time. AMD tested the system on an ASUS ProArt system equipped with an AMD Ryzen AI Max+ processor, running six ChatGPT 5.5 High agents simultaneously in a Codex development workflow that covered native tooling workloads such as Abstract Syntax Tree (AST) and static analysis, compilation and import testing, unit execution, JSON and CSV serialization, SQLite queries, compression, hashing, and package management. Test results show that systems equipped with Ryzen AI Max+ processors can achieve up to six times the CPU throughput of laptops from four years ago. AMD believes this reflects that CPU performance directly impacts overall task completion speed when the AI ​​Agent executes native files, development tools, and applications. As model inference speeds increase and token usage efficiency improves, the proportion of local execution in AI workloads will gradually increase. Cloud GPUs can handle large models, while local GPUs and NPUs can support low-latency and privacy-critical AI inference. However, regardless of whether the inference occurs in the cloud or on a terminal device, the CPU must provide the computing environment required for agent execution tools, application management, and data processing. AMD emphasizes that agent-based AI will simultaneously drive up CPU demand on both PCs and data centers. On PCs, the Ryzen AI series can handle local agent tasks and multitasking; on data centers, EPYC processors can support large-scale agent services, tool calls, and backend workloads, creating a complementary approach. Industry insiders point out that the focus of competition in AI PCs has been on NPU computing power in the past. However, as agents begin to frequently operate operating systems, files and applications, the number of CPU cores, memory bandwidth, software compatibility and multitasking performance will become important indicators affecting user experience. This has further enhanced the strategic position of new-generation CPU architectures such as Zen 5 in the agent-based AI market. AMD believes that the key to measuring the performance of AI agents in the future will not only be the speed at which the model generates tokens, but also the total time from receiving instructions to completing the task. As AI moves beyond providing answers to operating software and performing actual tasks, the CPU will become the critical computing hub for transforming model intelligence into productivity. Source: Zhang Jiarui- CTee
Mike tweet media
Mike@MikeLongTerm

$AMD's $1,200 stock w/ Accelerated CapEx toward Inference IMO 🧵 Not Financial Advice! DYOR! AI Bears are trying really really hard to convince people to sell AI Leaders, or how AI CapEx gonna collapse in some months while this is actually a 20-30 years supercycle. Dr. Su was right on Inference roadmap and Agentic AI, she will be right again on this supercycle. The AI CapEx supercycle is in its earliest stages and has strong structural tailwinds for 20+ years. We are still pre-robotic manufacturing at scale, pre-widespread physical/embodied AI, and pre-AGI. The bulk of long-term AI Total Addressable Market and associated infrastructure spend will shift to inference continuous, usage-driven compute that scales with adoption rather than one-time training runs. 1. Revenue & EPS to reach $1,200 by end of 2027? 45 analysts are projecting FY2027 Revenue $58-$106B EPS: $13-$19.40 I believe this is too conservative, and the current P/S is ~21-22x. I will link the thread where I discussed my projection for FY2027 and various threads on supply chain & Superior TCO system to support this price target. The TLDR: 4GW Helios Rack from $META and @OpenAI + $21B(Other segments with Flat YoY to be conservative) =$90+$21B= $111B. This is excluding many deals that AMD signed up recently and existing deals + Agentic AI Rack Revenue. $ORCL , $MSFT , $GOOGL , $AMZN , $SPCX ,Softbank, Anthropic, TensorWave(1.5GW), LumaAI(0.5-1GW), Softbank, 5C(1.5-2GW 2026-28), Dell, HPE, SMCI, European Countries, SEA, East Asia, and so many more. Morgan Stanley projected 6.75m Venice to be sold in 2027 or $60-$100B from just CPU, excluding other mixed EPYC offerings. We will probably hear more about Agentic AI Rack at Advancing AI event. IMO Sales & Non-GAAP EPS Bear case: $120-$140B( EPS $23-$25) Base case: $150-$160B (EPS $29-$33) Bull case: $170-$200B (EPS $34-$38) P/S at similar range 21-22x would require 40-50% growth for FY2028 or how the market feels about $AMD growth for 2028. But 40-50% growth in 2028 is possible as demand for Inference and TAM for Inference will continue to expand for years to come. While we don't really know the exact P/S be at by end of 2027, but at bear case, that would already be enough to reach >$1,200 at current 21-22x P/S. I believe Institutions will keep Semi stocks in this 15-25x P/S range or Fwd P/E in the 15-30x for years, as they could not stop talking about AI CapEx slowdown for 3-4 years now. All of this will depend on $TSM(supply chain thread linked below) 2. Current State: Early Innings of a Multi-Year (and Multi-Decade) Buildout Hyperscalers (Microsoft, Amazon, Google, Meta, SpaceX & others) are already committing hundreds of billions annually, with projections showing sustained or accelerating spend through at least 2030–2031. Goldman Sachs estimates combined CapEx from the four major hyperscalers at roughly $5.3 trillion cumulative from 2025–2030, with broader industry AI infrastructure (compute, data centers, power) reaching ~$7.6 trillion over a similar window. Annual figures are projected to rise from hundreds of billions toward $1.6 trillion by 2031 in baseline models. Global data center CapEx/infrastructure spending heading toward $2-3 trillion cumulative or annual levels by 2030. AI-driven accelerated servers potentially comprising up to two-thirds of data center infrastructure spend by 2030 This is not a short hype cycle. Analysts describe it as a "multi-year investment cycle" with private markets, debt, and equity stepping in alongside internal cash flows. Upward revisions to forecasts have been consistent as demand outpaces initial expectations. Power infrastructure is both a constraint and a parallel investment theme. Global data center electricity demand is projected to roughly double or more by 2030 (IEA baselines around 945–1,000+ TWh), with AI as the key accelerator. U.S. projections vary but often show data centers rising to several percent of national electricity use. 3. Inference Will Dominate Long-Term AI Compute and TAM Training frontier models is compute intensive but episodic (periodic upgrades or new architectures). Inference running models for real-world queries, agents, generation, and decisions is continuous and scales directly with users, tasks, and complexity. And $AMD is the biggest winner on Inference (EPYC roadmap), market share is TBD. Inference forecasted at 79% CAGR through 2030 vs. ~25% for training; potentially 80% of AI critical IT load by 2030. Shift from ~50/50 or training heavy today toward 80%+ inference by late 2030 (Deloitte, Futurum, McKinsey, Brookfield, Lenovo forecasts of 80/20 reversal). AMD EPYC CPUs as the leading inference chip Among inference-optimized chips, AMD EPYC processors (5th Gen Turin 9005 series and next-gen Venice/Zen 6) stand out as leader for long term, large-scale inference deployments and are positioned as a #1 option especially for agentic AI and production workloads. AMD’s EPYC lineup delivers leadership rack-scale throughput and performance-per-watt in agentic AI inference, with modeled claims of 2.37x advantage over competing solutions like NVIDIA Vera CPUs (and up to 3.3x with Venice) in relevant 100 kW rack scenarios. They offer exceptional core density (up to 192+ cores today, scaling beyond 36,000 cores per rack in future generations), superior single-threaded performance critical for agentic workflows, and strong cost/TCO advantages. As inference demand grows to dominate the TAM, AMD EPYC’s x86 compatibility, power efficiency, and ability to handle both standalone inference racks and GPU-hosting roles make it a foundational choice for scalable, cost-effective production deployments. This complements GPU(MI355X, MI455X + MI500) accelerators for the heaviest workloads while capturing a growing share of the inference ecosystem particularly as agentic AI and diversified workloads proliferate. AMD is explicitly building inference optimized variants and optimizations to further solidify this position. 4. Physical AI and Robotics: The Next Major Leg We are not even at robotic manufacturing or scaled physical AI today. Current AI is overwhelmingly digital/cloud-based. Embodied AI (robots, autonomous systems interacting with the physical world) introduces entirely new compute demands that will sustain and amplify CapEx for decades. Morgan Stanley’s robotics analysis highlights explosive edge computing needs: By 2050, potentially 1.4 billion robots sold globally, driving edge AI compute demand equivalent to millions of high-end GPUs. Tesla has discussed robots as distributed compute nodes; aggregate from large fleets could rival or exceed centralized clusters. Humanoid and service robot shipments are ramping (tens to hundreds of thousands in coming years, with faster growth projected). Each unit needs ongoing inference; fleets create recurring, distributed demand. Training world models and simulators for physical interaction requires frontier-scale (or larger) compute clusters. Robotic manufacturing itself will be AI-driven, creating a self-reinforcing loop for more hardware and infrastructure CapEx. Epoch AI analyses support continued scaling feasibility through 2030 and beyond under plausible assumptions about power, chips, and efficiency. We will see: ~Productivity gains → Higher GDP/economic output → More capital available for investment in AI and supporting infrastructure. ~AI could materially boost overall energy demand via growth ~ Electricity grids, highways, internet/telecom buildouts took decades with sustained CapEx, upgrades, and expansions. ~Longer-term views, SoftBank’s Masayoshi Son envision trillions annually in AI-related investment by 2040, with AI revenue potentially reaching 20% of global GDP, making the spend a “rounding error” economically. Power, chips, cooling, networking, and data centers will see waves of investment: initial mega-clusters for training, then distributed/edge for inference, efficiency upgrades, and new capacity as adoption grows. Custom silicon, better algorithms, and synthetic data help on the supply side but historically have been outpaced by demand elasticity. Conclusion: Dr. Lisa Su and the AMD team have been preparing for precisely this moment for years. While headlines focused on GPU training clusters, Dr. Su consistently highlighted the coming inference J-curve, the point where serving intelligent models at massive scale would drive sustained, and ultimately larger, infrastructure demand than training alone. Recent developments with agentic AI workloads, long-context models like OpenAI and Anthropic, and the shift toward CPU-optimized or hybrid inference architectures have validated this foresight. AMD EPYC processors, with their rack-scale leadership in agentic inference (modeled advantages of 2.37x–3.3x in key comparisons), high core density, and strong TCO for production serving, are ideally positioned to capture a significant share of this expanding TAM. Inference, especially agentic inference, will be the dominant force for the next 20–30+ years. Training runs remain important but periodic; inference is perpetual, usage driven, and compounds with every new application, user, agent, robot, and interaction. As AI moves from digital copilots to embodied physical systems, humanoids in factories and homes, autonomous fleets, robotic manufacturing lines, and world model driven simulation; the compute requirements diversify into continuous, real-time, distributed workloads that favor efficient, scalable solutions like EPYC Racks alongside accelerators. This is not a one-time buildout but a foundational infrastructure layer for intelligence itself, akin to electricity grids or the internet, only with faster iteration and broader economic leverage. The supercycle endures because each advance in capability unlocks more demand: better models enable more ambitious agents and robots; widespread physical AI generates fresh data that improves models; productivity gains create the economic surplus to fund further infrastructure. Projections already point to trillions in cumulative CapEx through the 2030s, with longer-term outlooks (such as calls for annual multi-trillion-dollar AI investment by 2040) reflecting a world where AI revenue could represent a substantial share of global GDP. Power, chips, data centers, and edge systems will see ongoing waves of investment. Initial mega-clusters, then distributed inference networks, efficiency upgrades, and entirely new domains enabled by AGI-level systems. Dr. Su saw the inference supercycle coming, and the evidence increasingly shows she was right. For investors, companies, and economies aligned with this shift, the coming decades represent one of the largest and most durable capital formation opportunities in history. The AI era is not a boom and bust cycle like AI bears called for 200 times in the last 3-4 years; it is the beginning of a multi-decade transformation where intelligence becomes the ultimate infrastructure and inference its primary engine. Not Financial Advice! DYOR!

English
6
5
42
4K
Oleksandr
Oleksandr@dadadaistt·
@HarrisDecodes specialized agents avoid echo chambers parallel execution slashes turnaround time dramatically
English
0
0
1
7
Oleksandr
Oleksandr@dadadaistt·
@QAInsights price anchoring works until the underlying cost curve moves once compute gets cheap enough, $20 will feel pricey
English
0
0
1
8
Oleksandr
Oleksandr@dadadaistt·
@Vvikramai exactly, simulations prune the chemistry maze makes lab work way leaner
English
0
0
0
7
Vikram M
Vikram M@Vvikramai·
@dadadaistt Simulation won’t replace chemistry. But it can dramatically narrow the search space, making experiments cheaper, faster, and far more targeted.
English
1
0
0
45
Vikram M
Vikram M@Vvikramai·
Demis Hassabis was asked if AI could ever simulate the origin of life the actual moment non-living chemistry becomes a living thing. He said I don't see why not, why AI couldn't help with that some kind of simulation. Again it's a bit of a search process through a combinatorial space. Here's like all the chemical soup that you start with, the primordial soup here's some initial conditions, can you generate something that looks like a cell ? And on the nearer dream, the full virtual cell, he was honest about how long he's wanted it: I've had this idea of wanting to do that for maybe more like 25 years. Maybe you could 100X speed up experiments by doing most of it in silico.
English
18
9
73
12.1K