Gazette

Vol. 43 Sunday, 9 November 2025
Vol. 43 9 Nov 2025

Cursor is a tightly knit, in-person startup focused on building developer tooling that blends UX and machine learning. They hire very selectively, favor self-motivated engineers, and rely on frequent internal feedback. The team cares deeply about code and aims to shape the future through ambitious product work.

6 highlights

As one very early document on Cursor’s culture noted, “Cursor probably ranks the highest in the world in terms of the average number of hours using the company’s main product per employee per week. The only real contender might be Apple with their Macs and iPhones.” Everyone at Cursor is using Cursor all the time.

One of my favorite Slack channels at Cursor is #braintrust, which includes everyone at the company. People use it to get feedback on what they’re building, often in the form of a vote using emojis. A real example to make this vivid: “cmd k – edit full file – 🟢 = REMOVE and 🔴 = ‘I use this and need it.’” This is in fact a very efficient and engaging way to get people to “pick sides,” and it often sparks productive debate.

Stripe had such a culture; my former boss/colleague/co-founder, Eeke, came up with the term “micro-pessimist, macro-optimist” to describe this way of operating. This also rings true at Cursor. While people can be very critical of execution, they’re also quite optimistic that they’re going to build something consequential, and generally frame things in terms of potential success rather than potential failure.

At Cursor, people poke and prod each other’s work a lot. This can be quite jarring for folks who haven’t operated in that kind of culture before. Top builders know what great products feel like, so people can get very opinionated about how things should work. They’ll liberally offer feedback on what is missing to hit the bar, and extra hands to help get it there.

Cursor is in no way dismissive of these users or the general ambition to democratize coding. But the company’s stance is very much that other companies can focus on lowering the floor, while Cursor will focus on raising the ceiling.

If you believe, like I do, that what we build is a function of how it feels to build it, what Cursor does has a real shot at meaningfully shaping the future world we experience

  • TIME_WAIT and its design implications for protocols and scalable client server systems #
    , 3 highlights

    Unfortunately the way some operating systems implement TIME_WAIT appears to be slightly naive. Only a connection which exactly matches the socket that's in TIME_WAIT need by blocked to give the protection that TIME_WAIT affords. This means a connection that is identified by client address, client port, server address and server port. However, some operating systems impose a more stringent restriction and prevent the local port number being reused whilst that port number is included in a connection that is in TIME_WAIT. If enough sockets end up in TIME_WAIT then new outbound connections cannot be established as there are no local ports left to allocate to the new connection.

    Given that TIME_WAIT affects outbound connection establishment due to the depletion of local port numbers and that these connections usually use local ports that are assigned automatically by the operating system from the ephemeral port range the first thing that you can do to improve the situation is make sure that you're using a decent sized ephemeral port range.

    For a server that does establish outbound connections as well as accepting inbound connections then the golden rule is to always ensure that if a TIME_WAIT needs to occur that it ends up on the other peer and not the server. The best way to do this is to never initiate an active close from the server, no matter what the reason. If your peer times out, abort the connection with an RST rather than closing it. If your peer sends invalid data, abort the connection, etc. The idea being that if your server never initiates an active close it can never accumulate TIME_WAIT sockets and therefore will never suffer from the scalability problems that they cause.

  • Researchers simulate an entire fly brain on a laptop. Is a human brain next? #
    , 2 highlights

    Shiu noted that scientists have already created whole brain diagrams and computer simulations for much smaller brains, such as that of a fruit fly larva, which has 3,016 neurons, and a nematode worm, which has 302 neurons. But computer simulations of these brains weren’t very good at predicting larval or worm behavior, perhaps because it’s harder to establish in these creatures which neurons are excitatory, that is, likely to activate downstream neurons, or inhibitory, which would silence downstream neurons. Thanks to decades of research, this is much better understood in the adult fruit fly brain.

    “We essentially ignore all of the different morphologies of individual neurons and assume all excitatory or inhibitory neurons work the same, which we know isn’t the case,”

  • Willingness to look stupid #
    , 1 highlight

    On the flip side, one of the most common failure modes I see with junior engineers is when someone will be too afraid to look stupid to ask questions and then learn very slowly as a result; in some cases, this is so severe it results in them being put on a PIP and then getting fired

  • Flounder Mode #
    , 1 highlight

    This shouldn’t make us defensive or self-conscious, but it does. I, like many others, want to be great. I want to feel commitment and camaraderie and work hard and be my best and impact top and bottom lines. But I don’t want to also feel tormented or be tortured into greatness or look in the mirror and wonder why I suck. But what does that say about me?

  • How to Keep Winning #