Weblog

Ref: “Introducing Cursor 2.0 and Composer”

I’m still figuring out the right granularity for a “Weblog,” but here’s a self-referential one: creating this new Weblog portion.

A couple days ago “Cursor 2.0” came out with their new model, Composer 1, and their new Agents tab in the VSCode editor.

I’m rather new to agentic coding. While at Figma, I only really used GitHub Copilot (the Tab autocomplete) and swore by it. Afterwards, I’ve been using mostly Claude Code which I enjoy and didn’t see a huge need to switch off of.

Pros: Cursor’s new UI + model all fits together in a way I’m bought into. Literally. I bought Cursor Pro and off we go! Also the model is really fast (200tok/sec) and is kind of addicting.

Cons: Composer 1 could get better at multimodal understanding. I yelled at it a few times about fixing spacing (given a screenshot).

About a month ago, I’d spend an hour on YouTube Shorts. Tired of that—I’d end up on Bluesky, then X. Read the news and get irritated. Futz around. Back to YouTube!

One day I had enough. No More Algorithms.

Getting off algorithms sounds agreeable enough, but I got off the news as well, which sounds like a trite and privileged thing to do. You could say, “not everyone can tune out!” and you’d have a fair point.

I’m not trying to “tune out” per se—at least not to the world’s problems. But the trap is to watch like it’s The Hunger Games, a state violence reality show. Ultimately, witnessing violence isn’t the same as helping.

My actual goal is to keep informed about the people being affected and try to help. This can be friends, family, or people I don’t know.

Can I do that without the news?

As the eagle-eyed among you may have noticed, I’ve been working on a new project for the past few months.

I’m incredibly thankful for my time at Figma—almost 3.5 years. It’s a great team; and while the largest company I’ve ever worked at, it still feels like a startup with the benefit of a massive and caring community. This is what I will miss most.

On the other side: I’ve been using the community space at South Park Commons in NYC, which I’d highly recommend. I love the positive entropy and talent density.

Ref: “My approach to running a link blog” by Simon Willison

I wanted to start link blogging! I’ve been very inspired by Simon Willison the past few years—and once I’ve gotten past having Something Important to say, a link blog seems like a good way to lower the stakes of making & sharing something on my website.

This is the main tenant:

I try to add something extra. My goal with any link blog post is that if you read both my post and the source material you’ll have an enhanced experience over if you read just the source material itself.

I’ve backfilled a few entries (and will more-so soon), and installed RSS if that’s your jam. Let me know what you think!

I helped make a game—SUB-SURFACE! A gamejam one, anyway—every year or so I end up doing a gamejam with a few friends.

Who worked on it:

Austin Breed (art & animation), Jeff Lee (programming & audio), me (programming), Saman Bemel-Benrud (a bit of everything), Tom Lubanovic (design)

Node.js packages, NPM post-install scripts horrify me.

So much of “traditional” security relies on if an application can get root, change your system etc… to say absolutely nothing about what’s sitting in your $HOME directory.

My SSH keys? My downloads? My private notes?

At any time—any of the bazillion packages NPM install could be malicious, and secretly exfiltrate your data. DYLD_INSERT_LIBRARIES something, put something in your .bashrc, whatever.

Another JavaScript runtime—Deno tries to solve this problem:

> deno run --allow-run runner.ts
error: Uncaught PermissionDenied: Requires env access to "HOME", run again with the --allow-env flag
const privateKey = await Deno.readFile(Deno.env.get("HOME") + "/.ssh/id_ed25519");

By default, access to most system I/O is denied. There are some I/O operations that are allowed in a limited capacity, even by default. These are described below.

To enable these operations, the user must explicitly grant permission to the Deno runtime. This is done by passing the --allow-read, --allow-write, --allow-net, --allow-env, and --allow-run flags to the deno command.

It started small, about a year ago, in-between me trying to finish my undergrad degree.

I kept having an idea for a spatial desktop manager—not totally unlike a project called PaperWM, although I didn’t know it at the time. You can think of like when you search for titles in Netflix how the different rows retain their relative position to the cursor. Except, of course, with windows.

Cut to a few months later, I ended up combing through stacks of Linux documentation trying to find the best way to build this thing.

OK. I need to learn about Wayland and build my window manager with that. Surely C isn’t good enough (in fairness, it isn’t), which compiled language has the best wlroots bindings? Swift, cool.

Maybe it needs to be a distro?

Cut later—I now have a fully immutable Linux system decently far removed from my Ubuntu base. This little immutability stunt, based on OSTree, is pretty stable actually. There’s a lot of externalities that come with it, and of course I had to figure those out as well from the jump. I took optimistic notes.

On and on it went, me finding the ends of the Linux earth for prior art and inspiration, but my excitement for the original idea was waning.

The goal of a side-project

If it’s not clear speaking of it in the past-tense, I’m no longer working on this project.

Was it a failure? I don’t know. I’m not sure. All of these tasks, some I’m actively invested in and others zombies, all carry a guilt that they’re not shipped. “Always be shipping.”

Other than declaring side-project bankruptcy, what am I suppose to do? Make a GAANT chart months out for my free time?