come build a cloud. we are doing everything from custom hardware to custom ssh servers to our own global load balancer. very senior small high-trust team looking for someone we can rely on to get done whatever is most important in the stack for the business. some days that means patch the vmm. other days it means figure out passkey quirks. more about what we are building here: https://crawshaw.io/blog/building-a-cloud email me at david@exe.dev.

Come build a new cloud. The entire engineering team has been in the industry 20+ years. Lots of hard problems. The freedom and responsibility to do what you think matters, push it to prod and deal with support when it breaks.

We are all busy discovering the shape of new tools and norms as our profession has been overturned by LLMs. It is not too surprising similar ideas are floating about. Though I have not seen anything that captured how I now go about personalizing programs, and how I expect it to change our industry. So I wrote this.

FWIW the first version of meat was based on anthropic models, I switched to Oai models because they are faster and just as good right now. This is an astonishing thing to say, but the switch was a single shot prompt using a frontier model. I’m happy to add some selector there, but that is also the point of this article: do you really need me to make it configurable when you can switch the tool over to Anthropic with a single prompt? It’s a strange new world we live in.

On the website: you’re right. I have some side-by-side diff examples I want to turn into a website. I am just short on hours in the day. My real goal is to make the tool compelling enough that I can convince my colleagues that we should build it into Shelley. :)

(We have a fix for this coming in a few weeks.)

It’s a real tension, working with a remote dev env has never been my first choice. But agents seem to tip the balance enough in favor of remote that I have switched.

This is why I have been avoiding the word sandbox for exe.dev. I don’t think developers agents need something “sandbox” shaped.

There is a good reason for this! In a large group of people, there are bad people.

This is also why I am done working at large companies. I learned a lot, met some great people, but am uninterested in a low trust environment. I like relying on my colleagues. When they do something unexpected, I am surprised and study it to learn, not lambast.

For years I have lamented the amount of paperwork necessary in most of modern programming to get things done. I don't know how important that is now that I have a machine fill out the paperwork. It would still be better if there was less fuss.

competitive salary, meaningful early equity, 2 days a week in the downtown sf office

come build a cloud. we are doing everything from custom hardware to custom ssh servers to our own global load balancer. very senior small high-trust team looking for someone we can rely on to get done whatever is most important in the stack for the business. some days that means patch the vmm. other days it means figure out passkey quirks.

more about what we are building here: https://crawshaw.io/blog/building-a-cloud email me at david@exe.dev.