Moodboard 3000 v3.0 is live. It's a @figma plugin that turns a pile of images into a real moodboard in one click. Four layout modes, up to 40 images, free. v3.0 adds subject-aware crops, remixing, video support, and a bunch more ↓

My latest project, “Tatebanko” (Mac, iPad, iPhone) to create interactive paper dioramas. Shown is a Hokusai tatebanko from @MFABoston Author shapes and folds, then build! Trace-to-cut, pinch-to-fold, and drag-to-position in an adjustable 3D scene. Sugoi!

Did you know that the .png format was created out of spite? Or that .jpeg just discards like half of the colours in your image because you won't notice? To celebrate last week's launch, I published a chapter on image compression. makingsoftware.com/chapters/…

The Figma MCP Server is now supported in Xcode #WWDC

Loops are still too manual. It's actually both more efficient and more token effective to let someone else manage the agents, produce the code, pay for the tokens, as well as run the company, while you do something entirely different professionally

I’m on AT&T fiber without a static IP, so if y’all are blocking based on IP you’ll want to update your database of tier-3 C nets

70k words, 600 illustrations, and 1000s of hours (so far). Making Software is now available in early access. makingsoftware.com/early-acc…

I'd like to tell you about a personal silly weekend project. Because I have love for the computing of the 90s, I built Relic, a tiny coding agent that runs on ancient devices. It fits on a floppy, needs 4MB of memory, and handles systems that were made before we got HTTPS. It's made with the same stuff used to build DOOM. It runs on Windows 95, a Wii, or the original Xbox. If you got a smart toaster, it'll probably run there, too. github.com/felixrieseberg/re…

𝙲𝚘𝚙𝚢𝚒𝚗𝚐... 📁📰📂🟦

Was an honor to chat about software at @southpkcommons with Soleio and everyone who showed up. SPC is a really special place

Rasmus Andersson @rsms believes the fundamentals of design aren’t changing with AI. Instead, they’re being amplified. New tools are a multiplier across the board. Higher quality. Faster shipping. Watch our full Design Chat at @southpkcommons below. A career highlight for me.

Although I have never worked on a game engine, I found this reference many years ago and instantly liked it. gameprogrammingpatterns.com/… It particularly discusses many foundations, from "how computer graphics work" to various design patterns used commonly in game engines. These patterns are interesting reads on their own, and you may find their usage elsewhere, too. Definitely worth reading and saving for later as a reference.

i mounted a tiny microphone on my apartment balcony to listen for any birds passing by and built a site to collage them as they're heard

I've got an agent in a loop optimizing a renderer with the goal to minimize frame times (and tests to measure). It got times down from 88ms to 2ms and allocations down from ~150K to 500. Sounds good, right? Wrong. This is exactly why agent psychosis is a big fucking problem. As an experiment, I rewrote the Ghostty core render state in Go, with access to identically laid out data structures as Ghostty and the exact same validation tests. I made a purposely naive renderer (simple, correct, but slow). 88ms per frame with 150,000 allocations (horrendous, lol)! I then kickstarted a Ralph loop to bring the frame times down. I told it it can't modify input data structures or the public API or tests (they're correct), but it can do anything else it wants. It got to work. It has worked for about 4 hours. I've spent around $350 on this experiment so far. The results? 88ms => 1.5ms 150K allocs => ~500 allocs Incredible right? Nope. My hand-written renderer I ported has frame times (same benchmark) of ~20us (0.020ms) and 0 allocations in the update path. This is the problem with psychosis and lacking systems understanding. If you don't understand the system, you're going to accept that this is an incredible result. If you understand the system, you'll see better solutions immediately and can do roughly 75x better on throughput. The people who blindly trust agent output are in the former camp. They're sheeple, overdrinking from a fountain of mediocrity. Standard disclaimer: I use AI all the time. I like AI. The point I'm making is to not blindly accept results. Think. Analyze. Learn.

I mentioned earlier that screen sizes and safe areas were the hardest part of developing Snap Shot Golf, but I’ve spent much more time on controls and interactions… It took many failed attempts before I realised I could use a second finger to shape shots like plucking a bow. 🏹

I like tools like these, which augments your workflow instead of replacing it. For example it’s a very tough sell to ask a programmer to switch text editors. Coding agents feel the same way; a product that asks you to use _their_ agent interface will have to pull me uphill