Miaoux

Building | AI + ERP for e-commerce growth brands

[vas @vasuman]

https://t.co/YlOT9k0U7E

[Haseeb ＞|＜ @hosseeb]

On the one hand, AI influencers are breathlessly raving about Claude Code, Clawdbot, and Cowork. And on the other hand, most people I know—even software engineers—are despondent, overwhelmed about how everything is changing so quickly. I hear this from people early in their careers especially, a fear that everything they've learned and the skills they've gained are rapidly being devalued.

This is a mental trap. Don't fall for it. You should not just be watching from the sidelines or reading articles about "how software engineering is changing."

Imagine it was 1993 and the personal computer revolution was kicking off. If you could go back in time to then, what should you have done?

The answer: try everything. Buy a PC. Learn how to touch type. Figure out what the Internet is. Imbibe it all. Don't wait until it becomes a job requirement.

That's exactly what you should do with AI. Try everything. Try Claude Code, try Clawdbot, try the Excel integrations, Veo, everything you can get your hands on. Learn what it's doing. Build your intuitions. Be one step ahead of it. Evolve alongside it. Don't lose your curiosity or get swallowed by anxiety or let yourself be convinced that you'll learn it when you have to. Think deeply about how AI will change the things around you—not society, that's too hard to project—but how it will change your job, your personal life, your immediate environment.

No matter how old you are or young you are, no matter what stage of your career you are in, we are all going through the biggest technological change of the last 100 years, and we're going through it together. Nobody has the answers. It's obvious that so much is going to change, but nobody is going to figure it out before you do if you choose to stay at the frontier.

So don't hide from it. Sit at the front of the class. Pay close attention. And be grateful that it's never been easier to stay at the frontier of the most important technology change of our lifetimes.

[Andrej Karpathy @karpathy]

A few random notes from claude coding quite a bit last few weeks.

Coding workflow. Given the latest lift in LLM coding capability, like many others I rapidly went from about 80% manual+autocomplete coding and 20% agents in November to 80% agent coding and 20% edits+touchups in December. i.e. I really am mostly programming in English now, a bit sheepishly telling the LLM what code to write... in words. It hurts the ego a bit but the power to operate over software in large "code actions" is just too net useful, especially once you adapt to it, configure it, learn to use it, and wrap your head around what it can and cannot do. This is easily the biggest change to my basic coding workflow in ~2 decades of programming and it happened over the course of a few weeks. I'd expect something similar to be happening to well into double digit percent of engineers out there, while the awareness of it in the general population feels well into low single digit percent.

IDEs/agent swarms/fallability. Both the "no need for IDE anymore" hype and the "agent swarm" hype is imo too much for right now. The models definitely still make mistakes and if you have any code you actually care about I would watch them like a hawk, in a nice large IDE on the side. The mistakes have changed a lot - they are not simple syntax errors anymore, they are subtle conceptual errors that a slightly sloppy, hasty junior dev might do. The most common category is that the models make wrong assumptions on your behalf and just run along with them without checking. They also don't manage their confusion, they don't seek clarifications, they don't surface inconsistencies, they don't present tradeoffs, they don't push back when they should, and they are still a little too sycophantic. Things get better in plan mode, but there is some need for a lightweight inline plan mode. They also really like to overcomplicate code and APIs, they bloat abstractions, they don't clean up dead code after themselves, etc. They will implement an inefficient, bloated, brittle construction over 1000 lines of code and it's up to you to be like "umm couldn't you just do this instead?" and they will be like "of course!" and immediately cut it down to 100 lines. They still sometimes change/remove comments and code they don't like or don't sufficiently understand as side effects, even if it is orthogonal to the task at hand. All of this happens despite a few simple attempts to fix it via instructions in CLAUDE . md. Despite all these issues, it is still a net huge improvement and it's very difficult to imagine going back to manual coding. TLDR everyone has their developing flow, my current is a small few CC sessions on the left in ghostty windows/tabs and an IDE on the right for viewing the code + manual edits.

Tenacity. It's so interesting to watch an agent relentlessly work at something. They never get tired, they never get demoralized, they just keep going and trying things where a person would have given up long ago to fight another day. It's a "feel the AGI" moment to watch it struggle with something for a long time just to come out victorious 30 minutes later. You realize that stamina is a core bottleneck to work and that with LLMs in hand it has been dramatically increased.

Speedups. It's not clear how to measure the "speedup" of LLM assistance. Certainly I feel net way faster at what I was going to do, but the main effect is that I do a lot more than I was going to do because 1) I can code up all kinds of things that just wouldn't have been worth coding before and 2) I can approach code that I couldn't work on before because of knowledge/skill issue. So certainly it's speedup, but it's possibly a lot more an expansion.

Leverage. LLMs are exceptionally good at looping until they meet specific goals and this is where most of the "feel the AGI" magic is to be found. Don't tell it what to do, give it success criteria and watch it go. Get it to write tests first and then pass them. Put it in the loop with a browser MCP. Write the naive algorithm that is very likely correct first, then ask it to optimize it while preserving correctness. Change your approach from imperative to declarative to get the agents looping longer and gain leverage.

Fun. I didn't anticipate that with agents programming feels *more* fun because a lot of the fill in the blanks drudgery is removed and what remains is the creative part. I also feel less blocked/stuck (which is not fun) and I experience a lot more courage because there's almost always a way to work hand in hand with it to make some positive progress. I have seen the opposite sentiment from other people too; LLM coding will split up engineers based on those who primarily liked coding and those who primarily liked building.

Atrophy. I've already noticed that I am slowly starting to atrophy my ability to write code manually. Generation (writing code) and discrimination (reading code) are different capabilities in the brain. Largely due to all the little mostly syntactic details involved in programming, you can review code just fine even if you struggle to write it.

Slopacolypse. I am bracing for 2026 as the year of the slopacolypse across all of github, substack, arxiv, X/instagram, and generally all digital media. We're also going to see a lot more AI hype productivity theater (is that even possible?), on the side of actual, real improvements.

Questions. A few of the questions on my mind:
- What happens to the "10X engineer" - the ratio of productivity between the mean and the max engineer? It's quite possible that this grows *a lot*.
- Armed with LLMs, do generalists increasingly outperform specialists? LLMs are a lot better at fill in the blanks (the micro) than grand strategy (the macro).
- What does LLM coding feel like in the future? Is it like playing StarCraft? Playing Factorio? Playing music?
- How much of society is bottlenecked by digital knowledge work?

TLDR Where does this leave us? LLM agent capabilities (Claude & Codex especially) have crossed some kind of threshold of coherence around December 2025 and caused a phase shift in software engineering and closely related. The intelligence part suddenly feels quite a bit ahead of all the rest of it - integrations (tools, knowledge), the necessity for new organizational workflows, processes, diffusion more generally. 2026 is going to be a high energy year as the industry metabolizes the new capability.

[Miaoux @miaoux]

If you're going to vibe. Do it properly.

[cogsec @affaan]

https://t.co/NscRA7sqBt

[Miaoux @miaoux]

Damn AI getting so good...

[錆たまご @Sabitamago]

使いたいショットが多くて尺がいつもより長尺(ﾟ～ﾟ)
Viduはエフェクトが派手なので好き🥰
#ViduAI #ViduCPP

[Miaoux @miaoux]

@epochbiz Link is 404 rn

[CoinSense @CoinSense_App]

Alpha-alpha version of CoinSense website is live!

It took longer than we wanted (mostly security hurdles), but the wait is over — the first version of our website is now online.

👉 What’s available today:
- CEX Top Accumulations → https://t.co/eQtZfTL7RJ
- CEX Top Holdings → https://t.co/9yMaMMcPKA
- DEX Top Accumulations → https://t.co/57tqAqpbeO
- DEX Top Holdings → https://t.co/QyzEnngdnw

🔑Access
- Premium users → full data unlocked automatically.
- Free users → see only rows 5–20 across all outputs.

🔐Auth
- Login via Discord
- Desktop → works directly.
- Mobile → must log in via Discord web (OAuth not supported inside Discord app).

🗒️Notes
The site is in super-alpha — no homepage yet, only these sections. But most of the backend is ready → expect shipping to accelerate fast from here.

📑Docs for the released sections:
- https://t.co/ey6lGdR30M
- https://t.co/l1PV9qjSdg
- https://t.co/PwiFFpWol6

Test it, break it, share it with others, give feedback. You’re shaping CoinSense with us 🤝

[Miaoux @miaoux]

Microstrategy. #strategy #microstrategy

But Solana. In your ROTH IRA / General Investment account / etc.etc. It goes up

$DFDV #dfdv #solana #stonks

[Miaoux @miaoux]

It’s joever. Can’t tell anymore.
Now link me to porn that can’t be distinguished from the real thing

[László Gaál @laszlogaal_]

Before you ask: yes, everything is AI here. The video and sound both coming from a single text prompt using #Veo3 by @GoogleDeepMind .Whoever is cooking the model, let him cook! Congrats @Totemko and the team for the Google I/O live stream and the new Veo site!

[Scotty.D.Russell @ScottyD_Russell]

Another weekend $BAM giga candle 🤣

This token has zero quit to it…

And that’s because of you, the Bam Fam!

Y’all are hustling like SOL is still at $8 in the middle of the bear. 🫡

[Crypto Meeks 🦦 @Crypto_Meks]

That’s the CA do your research

Devs last project on pump fun hit 100 million

He hacked pump fun - he’s followed by all the big names

No one has shilled it yet

At 370k mcap this is going to be huge !

raYuPPTp38hFaBHRtbgBfF354sYBvNTCi5vVDxSdwp6

@STACCoverflow

[Miaoux @miaoux]

$RAYIFY
Maybe?
https://t.co/A0ubW32Z6g

[Miaoux @miaoux]

Grok Pls.

[ThriveInChaos @ThriveInChaoss]

Few understand yet the virality of the pigeon , many will. $no

[Miaoux @miaoux]

$FIGURE MOAR - this thing has virality... make your own Action Figure - like everyone else is doing on chatgpt

[solgoodman @solgoodman]

Maybe you'll understand better this way

$LEGO TAKEOVER

[Miaoux @miaoux]

FREE Definitive $EDGE money for larger traders:

Addresses with over $100K cumulative volume traded from September 1, 2024 to February 28, 2025 on ANY of the following protocols are eligible:

Hyperliquid, Jupiter, Bananagun, Bullx, Photon, Odos, 0x, Cowswap, Drift

https://t.co/aJgPE3pxPU

[Bernie | Onchain Truths. @BernieOnChain]

I'll never $LEGO