i'm a frontend engineer and this weekend i wrote my first gpu kernels.
first question i asked: in the age of ai, does anyone still write these by hand?
short answer: yes. and that's exactly why i'm learning it.
a kernel is basically the callback you pass to array.map, except the gpu runs thousands of copies at once. each copy uses its index to find the one pixel or number it owns.
ai can already write the simple ones. i had an agent walk me through a greyscale filter in webgpu and it handled the boilerplate fine.
but the bugs that matter are subtle. drop one term from the index math and thousands of threads race to write the same slot. the output looks almost right. nothing crashes.
that's the pattern with agents everywhere: they write the first draft, you own whether it's correct. and you can't review a kernel you don't understand.
the kernels that make models faster, like flashattention, are still written or closely guided by people who know the hardware.
my plan: fundamentals in webgpu first, then triton and cuda.
shipping with agents doesn't mean knowing less. it means knowing enough to catch what they get wrong.
i'll share what i learn as i go.
4
6
425
Introducing Canva Craft 🚀
Extraordinary image generation is now available to everyone, powered by our first frontier model built specifically for design.
With Craft, Canva is now the world's second most advanced AI lab for image generation on @DesignArena's global leaderboard.
See what it can do 👇
Ciro Nunes retweeted
Give your agent a way to verify its work. This can dramatically improve the quality of output.
With this process in place, Claude Code was able to write 90%+ of its code itself. When generating software at a faster rate than you can review it, the bottleneck shifts to proving that it works. @bcherny and team invested enough in verification, we've been able to move fast while maintaining stability.
Code reviews aren't going away, but you need to think of it differently. One human reading through line-by-line is no longer going to work as a gate, it needs to evolve into a multi-layered verification system, built with fast deterministic feedback loops for your agents.
This is where e2e tests, feature maps (as @poteto has been advocating), property tests and multi-agent adversarial reviews come in. These all provide opportunities to catch errors early and fix them before things get out of hand.
You don't have enough eyeballs for the amount of code being written so your focus needs to be on product intent, risk assessment and evaluating evidence rather than reviewing code. Delegate the code checking work to your automated tests, scale your approvals based on risk, and turn your test failures into living evaluations. This approach helps maintain speed without losing reliability.
Let the agents do what they do best and let you focus on what makes you irreplaceable: judgement, direction, and ownership. We tried to capture how we handle code review and verification in this writeup. Hopefully it's helpful.
Claude writes about 90% of Claude Code's code.
From June to September, merged PRs more than doubled while the share reverted fell by more than 40%.
We wrote about how we changed code review to get there, and how to adopt it:
claude.dev/blog/solving-code…
Ciro Nunes retweeted
This guy re-created all the adobe apps with opus-5.5, ported them to rust, and opensourced them
something really cool is happening
Readers added context they thought people might want to know
These projects are partial open-source Rust reimplementations of Adobe apps (built rapidly with AI agents), not complete recreations; their READMEs and roadmaps document many missing features and features still in development.
github.com/storytold/phot…
github.com/storytold/vect…
github.com/storytold/vect…
github.com/storytold/film…
github.com/storytold/film…
github.com/storytold/ligh…
getartcraft.com
Ciro Nunes retweeted
If someone asks you how to set up a software factory, send them this
notice how LLMs add many unnecessary UI elements?
if it serve no purpose, get rid of it.
less is more
89
Ciro Nunes retweeted
how cyclomatic complexity audits can fix your slop code
drops from 91 decision paths → 12
what if we could quickly identify how we spend our money and potential saving opportunities and have agents making it happen?
1
84
Ciro Nunes retweeted
This was wild to watch unfold. We ran 𝚒𝚜-𝚊𝚐𝚎𝚗𝚝𝚒𝚌 in a loop against is-agentic.com until it got to 100/100.
It made us close quite a few gaps. We worked hard to make sure the criteria is high quality and worth your time & tokens.
Introducing is-agentic.com, a tool to measure how well agents can read your site. Backed by @oradotai's research, you can run:
▪︎ Audits with 100+ checks
▪︎ Visualizations of agents using your site
▪︎ One-click prompts to fix problems
▪︎ A CLI for agents
🧵 4/5: Step 2 — JavaScript Reads the Raw Bytes
JS takes that integer offset and reads directly from the shared memory buffer:
1
18
🧵 5/5: The Takeaways
Pointers = Array Indices: A Wasm pointer is just an offset into WebAssembly.Memory.
Zero-Copy Speed: JS reads the guest's memory directly, avoiding serialization overhead.
Watch Out: Memory must be freed manually (or via wasm-bindgen) to avoid memory leaks!
If you found this useful, RT the first tweet and follow for more Rust + WebAssembly deep dives! 🚀
19
Ciro Nunes retweeted
You're not depressed brother. You just need to vibe code a useless app nobody cares about.















