when the dream becomes the job i used to think the dream was to make my hobby my work. to spend my life close to the things i loved: computers, tools, interfaces, systems, tiny details, the feeling of making something from nothing. the things i used to do at night, after school, after work, in the margins of life, somehow became the center of my life. and it is a dream. i don’t want to pretend otherwise. there is a very specific happiness in getting paid to care. in meeting other people who care. in building a language around your obsession. in seeing something that lived only in your head become real enough for other people to touch. but there is also a quiet pain in it. because the thing that once belonged only to you no longer belongs only to you. it becomes attached to deadlines, teams, customers, strategy, money, reputation, momentum... curiosity becomes roadmap. taste becomes decision-making. play becomes output. the thing you once used to escape the world becomes the thing through which the world reaches you. and now there is another strange layer: the machines are getting good at the work too. not just the boring parts. the parts that used to feel close to the heart. writing, coding, designing, reasoning, making taste-like decisions, turning vague ideas into something real. the things we once used as proof that we had something special inside us are becoming things a model can approximate, remix, and sometimes do faster. that can feel scary in a very specific way. not only because of jobs or competition, but because it touches the myth you built around yourself. if the thing i became good at can be done by a machine, then what part of it was really me? i think that question is painful because it arrives at the same place. the original love. before the title, before the company, before the taste became a role, before the work became useful to other people, there was a small fire inside. curiosity. obsession. the feeling that the world became more alive when you understood a little more of it, or made a tiny piece of it bend to your will. AI can make the output faster. it can even raise the floor of the craft. but it cannot want on your behalf. it cannot decide what is worth loving. it cannot protect the strange private thread that made you care in the first place. maybe that is what becomes more important now. not whether you can still produce the artifact by hand. not whether you can outperform the machine at every task. that game is already changing. the real question is whether you still have a relationship with the source. the part with no audience. no roadmap. no deadline. the part that can wander, collect strange references, make useless things. follow beauty, be wrong, be slow, be you, be true. because that part is not separate from the work. it is the source of the work. if you lose it, you can still operate. you can still manage the machine. you can still prompt, review, decide, ship, and keep things moving. but the work becomes thinner. safer. more explainable. less alive. so maybe the real discipline is not to work harder, rest more, or care less. maybe it is to keep returning to the place where the love began – before it became useful, before it became legible, before anyone needed anything from it, before even the machine could mirror it back to you. not to escape the work. to make sure the fire inside is still alive.

Cursor is hiring design engineers. looking for people with taste, systems thinking, and deep care for fast, polished experiences – especially folks excited to build the tools that help designers, engineers, and agents ship quality code. know someone? tag them or DM me 📧

from apps to material software used to be something you opened an app was a room with walls: calendar here, notes there, music there, work there. each one had its own logic, buttons, its own little kingdom. the user moved between kingdoms, carrying context in their head but ai starts to break the walls software becomes less like a destination and more like material. something you shape, combine, stretch, ask, remix, and leave behind as traces. a document can become an app. a conversation can become a workflow. a song can become a memory. a task can become an agent. the boundary between using and making gets blurry the old model was: choose the right tool for each task the new model is: express the shape of the thing you want, then refine it with the system you built this changes the role of the interface. ui is no longer only fixed views for fixed functions. it becomes a surface where intent turns into structure. the best interfaces will feel less like menus and more like clay – responsive, persistent, inspectable, and alive apps won’t disappear. rooms are still useful. but the deeper shift is that software stops being a set of sealed containers and becomes a medium people can think through like paper, but executable like language, but spatial like memory, but programmable software stops being something only programmers make it becomes material anyone can shape