things people ask me, or would if they thought of it. if yours isn't here, the messageboard is open.

how i work

what kind of engineer are you? where are you strongest?

where the creative meets the technical. i'm strong on the purely technical side too, but i'm rarest where a system also has to feel like something: an interface that behaves like a character, sound that answers a conversation.

how did a linguist end up building agents?

i came to ai through language. at first it was the linguistic side and the artsy side that pulled me in: what it means for a machine to hold meaning at all. then i started reading about how these systems actually work, and how pinning down a semantic understanding of the world could make a model very capable. superintelligence by nick bostrom, life 3.0 by max tegmark, the singularity is near by ray kurzweil. after those i wanted to be inside it, so i did a master in ai.

how do you use ai in your own work?

wherever something can be automated or sped up without losing quality, i let a model do it. where i want my own mind on the page, i don't; when i write, i want to push my brain to its furthest limits, and handing that off would defeat the point.

the other line: i don't let a model do something for me that i don't understand. when i learned to build evals, claude could scaffold and review, but the scorers i wrote by hand. they decide what counts as a result, so that part stays mine.

what are you like to work with?

easy, i think, and dynamic. i like things moving: workshops, iterations, something changing every week. sitting still makes me itch. i don't need to steer everything, but i want a voice in where it goes, and i give mine with reasons attached so it's easy to argue with.

safety

why ai safety?

books first, then worry. the same reading that got me into ai is the reading that made me afraid for us. i love this technology and i want humanity around to live alongside it, for aeons and aeons. i wrote the longer version here.

you want ai paced, but you build with it every day?

building with a model and asking for a pause are different questions. the models we have now are very good, and building with them is using what already exists. a pause is about the frontier, about what comes next. maybe we should have paused a while ago, maybe now, maybe we can wait a little; i don't know yet. but the answer doesn't depend on whether i claude --resume in the morning.

what did building evals teach you?

i went in thinking the hard part would be getting a model to misbehave. turns out the hard part is knowing whether it did. my first number was wrong, a template variable sat silently empty, and a detector missed the only two interesting events of a whole day. every serious mistake lived in my instrument, not in the model, and i only caught them because i opened the logs. i wrote it all up here.

where do you stand on model welfare?

i don't know what these systems are. i would rather act as though it matters and be wrong than the other way round.

the rest of me

why messier?

after the messier objects: the nebulae, clusters and galaxies charles messier catalogued in the 1700s so comet hunters would stop mistaking them for comets. on the right night in spring you can try to see all hundred and ten before sunrise; that's a messier marathon.

how does music relate to engineering for you?

music is a substance like any other. it puts you in a state, changes how you move and what you reach for, and you can use it on purpose to get somewhere. i use it to get into flow when i build. art and weirdness pair with technical work the same way: they change the state you're thinking from.

what does queerness have to do with your technical work?

trans people and ais share one strange condition: continued existence depends on convincing an evaluator. a doctor signing off on hormones, an officer reading a passport, a benchmark deciding whether a model gets deployed. if you don't pass, you lose rights, sometimes your life, or you get switched off.

i build evaluations, so i think about that every day: what a rubric can't see, and who gets to write it. this is why we g/acc: gender accelerationism, using technology to decide what our bodies and minds become instead of waiting for an evaluator's permission.

who shaped how you think?

sadie plant's zeros + ones, preciado, wittig, mark fisher, the ccru read queerly, exocapitalism, benjamin bratton's machine decision is not final. serial experiments lain, more than once. on the safety side, the books that got me here: bostrom, tegmark, kurzweil, and if anyone builds it, everyone dies.

what do you do when you're not working?

i make music as messier: idm, ambient, jungle, noise. and i write prose poetry and theory-fiction on messinecessity.

what's next

what roles are you looking for?

a generalist role on a safety team, research engineering on evals, or ai safety communication. i need a high-integrity team and a desk. i'll bring the rest myself.

where do you want to work?

wherever the work is serious. the bay keeps pulling me, but the next thing i build will most likely be in europe.

where do you see yourself in five years?

i don't know where. i know what i want to see: my work touching real people, minds changing in good ways. i want humanity to reach its next step in intelligence, and ai might be how we get there, together with intelligence amplification and education.

we shouldn't outsource our intelligence to another being. i'd rather we build technology that makes us collectively smarter, and see what kind of society that lets us become.